linux-kernel - Re: [PATCH] powerpc: build dtb even without COMPILE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 4 Jan 2019 11:46:47 -0600
From:   Rob Herring <robh+dt@...nel.org>
To:     Corentin Labbe <clabbe@...libre.com>
Cc:     Benjamin Herrenschmidt <benh@...nel.crashing.org>,
        Mark Rutland <mark.rutland@....com>,
        Michael Ellerman <mpe@...erman.id.au>,
        Paul Mackerras <paulus@...ba.org>, devicetree@...r.kernel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: [PATCH] powerpc: build dtb even without COMPILE_TEST

On Fri, Jan 4, 2019 at 3:58 AM Corentin Labbe <clabbe@...libre.com> wrote:
>
> I wanted to test the virtex440-ml507 qemu machine and found that the dtb
> for it was not builded.

Just do:

make virtex440-ml507.dtb

> All powerpc DTB are only built when CONFIG_OF_ALL_DTBS is set which depend on
> COMPILE_TEST.
> But building DTB is not related to a "compile build test".

But it is. We normally only build the dtbs for enabled platforms just
like we only build platform/driver code for enabled platforms. It's
hidden behind COMPILE_TEST so it only gets enabled for
allmodconfig/allyesconfig builds.

> So this patch made building of DTB independent of COMPILE_TEST (by
> depending only on the PPC arch)
> A better selection of which DTB to build could be done in the future
> like that do the ARM arch.

No reason you can't start that now for the platform you care about.
You don't have to convert everyone.

Rob