From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] linux: Support multiple device tree build
Date: Fri, 21 Dec 2012 13:26:48 +0100 [thread overview]
Message-ID: <87txrf8ubb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <50D45441.4050704@mind.be> (Arnout Vandecappelle's message of "Fri, 21 Dec 2012 13:21:21 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> Not directly related to your patch, but this is broken by the recent
>> (post-3.7) change to put .dtb files in arch/arm/boot/dts. I wonder how
>> the best way of handling this is?
Arnout> How about adding this to LINUX_POST_PATCH_HOOKS
Arnout> if [ ! -e $(KERNEL_ARCH_PATH)/boot/dts ]; then \
Arnout> ln -s . $(KERNEL_ARCH_PATH)/boot/dts; \
Arnout> fi
Arnout> and adding dts to the path everywhere we use it?
That won't work as boot/dts exists (that's where the .dts files
are). The only thing that changed was where the generated .dtb files are
put (in arch/$ARCH/boot vs arch/$ARCH/boot/dts).
I solved it by adding a bit of extra logic to the LINUX_INSTALL_DTB rule
instead.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2012-12-21 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 8:48 [Buildroot] [PATCHv3] linux: Support multiple device tree build Maxime Ripard
2012-12-20 14:24 ` Peter Korsgaard
2012-12-21 12:21 ` Arnout Vandecappelle
2012-12-21 12:26 ` Peter Korsgaard [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-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=87txrf8ubb.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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