From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: uImage with integrated dtb file
Date: Mon, 26 Mar 2012 18:48:23 +0200 [thread overview]
Message-ID: <4F709DD7.2080606@antcom.de> (raw)
In-Reply-To: <4F7085DA.6030402@wwwdotorg.org>
On 26/03/12 17:06, Stephen Warren wrote:
>> quiet_cmd_uimage = UIMAGE $@
>> - cmd_uimage = $(CONFIG_SHELL) $(MKIMAGE) -A arm -O linux -T kernel \
>> + cmd_uimage = cat $< arch/arm/boot/*.dtb > $<.tmp ; \
>
> That won't work well when multiple .dtb files are built.
That's completely correct! Therefore I called it "hack" (maybe
forgetting to prefix it "ugly"), so please don't use it. ;-)
Roland
WARNING: multiple messages have this Message-ID (diff)
From: Roland Stigge <stigge@antcom.de>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: devicetree-discuss@lists.ozlabs.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: uImage with integrated dtb file
Date: Mon, 26 Mar 2012 18:48:23 +0200 [thread overview]
Message-ID: <4F709DD7.2080606@antcom.de> (raw)
In-Reply-To: <4F7085DA.6030402@wwwdotorg.org>
On 26/03/12 17:06, Stephen Warren wrote:
>> quiet_cmd_uimage = UIMAGE $@
>> - cmd_uimage = $(CONFIG_SHELL) $(MKIMAGE) -A arm -O linux -T kernel \
>> + cmd_uimage = cat $< arch/arm/boot/*.dtb > $<.tmp ; \
>
> That won't work well when multiple .dtb files are built.
That's completely correct! Therefore I called it "hack" (maybe
forgetting to prefix it "ugly"), so please don't use it. ;-)
Roland
next prev parent reply other threads:[~2012-03-26 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 23:48 uImage with integrated dtb file Roland Stigge
2012-03-25 6:21 ` Dirk Behme
2012-03-25 11:48 ` Thierry Reding
2012-03-26 15:06 ` Stephen Warren
2012-03-26 15:06 ` Stephen Warren
2012-03-26 16:48 ` Roland Stigge [this message]
2012-03-26 16:48 ` Roland Stigge
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=4F709DD7.2080606@antcom.de \
--to=stigge@antcom.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.