From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Build a uImage with dtb already appended
Date: Thu, 15 Jan 2015 10:45:14 +0000 [thread overview]
Message-ID: <20150115104514.GD12302@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1421287693-23383-1-git-send-email-ottxor@gentoo.org>
On Wed, Jan 14, 2015 at 07:08:13PM -0700, Christoph Junghans wrote:
> Add new targets to build zImage and uImage with DTB appended (i.e. make
> 'uImage-dtb.am335x-bone' or 'make zImage-dtb.omap3-evm').
>
> Signed-off-by: Jeremy Kerr <jeremy.kerr@canonical.com>
> Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> Signed-off-by: Domenico Andreoli <domenico.andreoli@linux.com>
> Signed-off-by: Christoph Junghans <ottxor@gentoo.org>
> ---
>
> I don't know why this never got merged, but I think it is still useful.
What do you do about supplying the load address argument to mkimage,
which is highly platform specific?
This may be useful if you want to create one uImage for one platform,
but it's not useful in other cases.
However, in general, I don't want to augment the u-boot crap that we
already have in the kernel; it's too inflexible. You're much better
off taking the zImage and DTB, combining them yourself, and then
_if_ you insist on using the u-boot legacy format, running mkimage.
The alternative is to move forward with your uboot skills, and see
whether your uboot supports loading the fdt and use bootz with the
zImage instead of bootm.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2015-01-15 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 14:31 [PATCH] Build a uImage with dtb already appended Grant Likely
2011-08-02 15:33 ` [PATCH] fix for: " Nicolas Ferre
2012-06-29 20:39 ` [PATCH v2] Build a zImage or " Domenico Andreoli
2015-01-15 2:08 ` [PATCH] Build a " Christoph Junghans
2015-01-15 2:31 ` Olof Johansson
2015-01-15 7:33 ` Willy Tarreau
2015-01-15 10:45 ` Russell King - ARM Linux [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=20150115104514.GD12302@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).