From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Alan Ott <alan@softiron.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Leif Lindholm <leif.lindholm@linaro.org>,
"Gao, Liming" <liming.gao@intel.com>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [PATCH edk2-platforms] Platform/OverdriveBoard: move device tree compilation into build
Date: Tue, 29 Aug 2017 20:28:31 +0100 [thread overview]
Message-ID: <CAKv+Gu_ZaqRGu-FiLn=v1u9h=c7_uqaetP-Tza2Tc4_SondBUw@mail.gmail.com> (raw)
In-Reply-To: <f0611bfa-d383-2d5e-68fc-58f4ae6c2b39@softiron.com>
On 29 August 2017 at 20:26, Alan Ott <alan@softiron.com> wrote:
> On 08/29/2017 12:27 PM, Ard Biesheuvel wrote:
>>
>> Use the proposed BaseTools support for device tree compilation to
>> build the device tree binary from source at build time. Give it its
>> own .inf and a build rule so the tools take care of everything.
>>
>> Contributed-under: TianoCore Contribution Agreement 1.1
>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> ---
>> Platform/AMD/OverdriveBoard/FdtBlob/styx-overdrive.dtb
>> | Bin 9357 -> 0 bytes
>> Platform/AMD/OverdriveBoard/FdtBlob/styx-overdrive.dts
>> | 510 --------------------
>> Platform/AMD/OverdriveBoard/OverdriveBoard.dsc
>> | 1 +
>> Platform/AMD/OverdriveBoard/OverdriveBoard.fdf
>> | 9 +-
>>
>> Platform/AMD/OverdriveBoard/OverdriveBoardDeviceTree/OverdriveBoardDeviceTree.dts
>> | 487 +++++++++++++++++++
>>
>> Platform/AMD/OverdriveBoard/OverdriveBoardDeviceTree/OverdriveBoardDeviceTree.inf
>> | 28 ++
>> 6 files changed, 521 insertions(+), 514 deletions(-)
>
>
> I like this in principle, but what's the 23 line difference in the DTS
> and/or should it be in a separate patch from the patch that moves the file
> so the difference is clear?
>
Yeah, fair point. Once the upstream prerequisite patch is merged, I
will split this into 2 or 3 patches.
prev parent reply other threads:[~2017-08-29 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 16:27 [PATCH edk2-platforms] Platform/OverdriveBoard: move device tree compilation into build Ard Biesheuvel
2017-08-29 19:26 ` Alan Ott
2017-08-29 19:28 ` Ard Biesheuvel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKv+Gu_ZaqRGu-FiLn=v1u9h=c7_uqaetP-Tza2Tc4_SondBUw@mail.gmail.com' \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox