From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit branch/next] linux: allow both in-tree and custom dts files
Date: Mon, 26 Feb 2018 09:11:06 +0100 [thread overview]
Message-ID: <87606ktbl1.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180225190328.GD2276@scaer> (Yann E. MORIN's message of "Sun, 25 Feb 2018 20:03:28 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Simon, All,
> On 2018-02-25 17:19 +0100, Arnout Vandecappelle spake thusly:
>> commit: https://git.buildroot.net/buildroot/commit/?id=382fe9f9261812682eab2d35e47aa94dc554380e
>> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/next
>>
>> For some boards, for example the Raspberry Pi, it's necessary to build
>> in-tree dts files as well as custom/out of tree dts-files (dt-blob.bin).
>> The existing logic made these two options exclusive, this commit changes
>> that to allow both in-tree as well as custom sources for dts files.
> This breaks all our cufrrent defconfig files that build a DTB, like
> for example configs/stm32f429_disco_defconfig, because the default
> that was implied by a choice is no longer true, so we need to add
> BR2_LINUX_KERNEL_USE_INTREE_DTS=y to those defconfig files.
That still doesn't fix it for any external defconfig. Adding a 'default
y' to BR2_LINUX_KERNEL_USE_INTREE_DTS will likewise break it for users
of BR2_LINUX_KERNEL_USE_CUSTOM_DTS. Perhaps we can change the logic to
look for nonempty BR2_LINUX_KERNEL_INTREE_DTS_NAME /
BR2_LINUX_KERNEL_CUSTOM_DTS_PATH variables?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-02-26 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 16:19 [Buildroot] [git commit branch/next] linux: allow both in-tree and custom dts files Arnout Vandecappelle
2018-02-25 19:03 ` Yann E. MORIN
2018-02-26 8:11 ` Peter Korsgaard [this message]
2018-02-26 22:06 ` Yann E. MORIN
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-all 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=87606ktbl1.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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