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:   Wed, 24 Feb 2021 19:32:45 -0600
From:   Frank Rowand <>
To:     Rob Herring <>,
        Geert Uytterhoeven <>
Cc:     Viresh Kumar <>,
        Pantelis Antoniou <>,
        Masahiro Yamada <>,
        Michal Marek <>,
        Vincent Guittot <>,
        Linux Kernel Mailing List <>,, Bill Mills <>,
        David Gibson <>,
        linux-kbuild <>
Subject: Re: [PATCH V7 4/6] kbuild: Add support to build overlays (%.dtbo)

On 2/5/21 3:08 PM, Rob Herring wrote:
> On Fri, Feb 05, 2021 at 11:17:10AM +0100, Geert Uytterhoeven wrote:
>> Hi Viresh,
>> On Fri, Feb 5, 2021 at 10:55 AM Viresh Kumar <> wrote:
>>> On 05-02-21, 10:41, Geert Uytterhoeven wrote:
>>>> On Fri, Feb 5, 2021 at 10:25 AM Viresh Kumar <> wrote:
>>>>> On 05-02-21, 10:02, Geert Uytterhoeven wrote:
>>>>>> Thanks for your patch
>>>>>> (which I only noticed because it appeared in dt-rh/for-next ;-)
>>>>>> On Fri, Jan 29, 2021 at 8:31 AM Viresh Kumar <> wrote:
>>>>>>> Add support for building DT overlays (%.dtbo). The overlay's source file
>>>>>>> will have the usual extension, i.e. .dts, though the blob will have
>>>>>> Why use .dts and not .dtso for overlays?
>>>>>> Because you originally (until v5) had a single rule for building .dtb
>>>>>> and .dtbo files?
>>>>> I am fine with doing that as well if Rob and David agree to it. Rob
>>>>> did suggest that at one point but we didn't do much about it later on
>>>>> for some reason.
>>>>> FWIW, this will also require a change in the DTC compiler.
>>>> Care to explain why? I've been using .dtsi for ages in
>>> I don't see you building them anywhere, they aren't added to the
>>> Makefile ever. What am I missing ?
>>> actually none of the dtso's were added to any makefile in that branch.
>> E.g. "ARM: dts: Build all overlays if OF_OVERLAY=y"?
>>> Anyway, the DTC needs to know how to treat the dtso format and it will
>>> error out currently with unknown format kind of errors.
>>> Below email [1] have some information on the kind of changes required
>>> here. Also note that we had to do similar changes for dtbo earlier
>>> [2].
>>> --
>>> viresh
>>> [1]
>> -@ is handled by "kbuild: Enable DT symbols when CONFIG_OF_OVERLAY is used"
>>> [2]
>> I never had a need for those changes to dtc. .dtso/.dtbo work fine regardless.
> I think what Viresh means is dtc won't automatically set the input type 
> to dts if not .dts.
> We stuck with .dtbo as it's already widely used. I don't know about 
> dtso though. If there's strong consensus to use .dtso, then let's do 
> that. Whatever color for this shed you like.

I overlooked this and mistakenly thought that the move to .dtbo also
involved changing to .dtso.  My bad.

My favorite color here is to use .dtso for the source file that will
be compiled to create a .dtbo.

Linus has already accepted patch 4/6 to 5.12-rc1, so changing to .dtso
will require another patch.


> Rob

Powered by blists - more mailing lists