[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200120181708.GN3697@linaro.org>
Date: Mon, 20 Jan 2020 18:17:14 +0000
From: Steve McIntyre <steve.mcintyre@...aro.org>
To: Rob Herring <robh+dt@...nel.org>
Cc: David Gibson <david@...son.dropbear.id.au>,
Alexandre Torgue <alexandre.torgue@...com>,
Frank Rowand <frowand.list@...il.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Michal Marek <michal.lkml@...kovi.net>,
Simon Glass <sjg@...omium.org>, devicetree@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Devicetree Compiler <devicetree-compiler@...r.kernel.org>
Subject: Re: [RFC PATCH 1/3] dtc: Add dtb build information option
On Fri, Jan 17, 2020 at 08:43:23AM -0600, Rob Herring wrote:
>On Fri, Jan 17, 2020 at 6:26 AM David Gibson
><david@...son.dropbear.id.au> wrote:
...
>> What might be better would be to have a dtc option which force appends
>> an extra .dts to the mail .dts compiled. You can then put an overlay
>> template in that file, something like:
>>
>> &{/} {
>> linux,build-info = /incbin/ "build-info.txt;
>> }
>
>I like this suggestion either as an include another dts file or an
>overlay. The latter could be useful as a way to maintain current dtb
>files while splitting the source files into base and overlay dts
>files.
ACK, that sounds like it could be helpful.
>But no, let's not prepend this with 'linux'. It's not a property
>specific for Linux to consume.
Right. We might be seeing the data coming through from U-Boot (or any
other random bootloader) too.
Cheers,
--
Steve McIntyre steve.mcintyre@...aro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
Powered by blists - more mailing lists