From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] linux: Support multiple device tree build
Date: Fri, 21 Dec 2012 13:21:21 +0100 [thread overview]
Message-ID: <50D45441.4050704@mind.be> (raw)
In-Reply-To: <87txrgyf5y.fsf@dell.be.48ers.dk>
On 20/12/12 15:24, Peter Korsgaard wrote:
>>>>>> "Maxime" == Maxime Ripard<maxime.ripard@free-electrons.com> writes:
>
> Maxime> Signed-off-by: Maxime Ripard<maxime.ripard@free-electrons.com>
>
> Committed, thanks.
>
> Maxime> define LINUX_INSTALL_DTB
> Maxime> - cp $(KERNEL_ARCH_PATH)/boot/$(KERNEL_DTS_NAME).dtb $(BINARIES_DIR)/
> Maxime> + cp $(addprefix $(KERNEL_ARCH_PATH)/boot/, \
> Maxime> + $(addsuffix .dtb, $(call qstrip, $(KERNEL_DTS_NAME)))) \
> Maxime> + $(BINARIES_DIR)/
>
> 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?
How about adding this to LINUX_POST_PATCH_HOOKS
if [ ! -e $(KERNEL_ARCH_PATH)/boot/dts ]; then \
ln -s . $(KERNEL_ARCH_PATH)/boot/dts; \
fi
and adding dts to the path everywhere we use it?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-12-21 12:21 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 [this message]
2012-12-21 12:26 ` Peter Korsgaard
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=50D45441.4050704@mind.be \
--to=arnout@mind.be \
--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