From: florian@openwrt.org (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: Device tree.
Date: Tue, 17 Jul 2012 14:41:35 +0200 [thread overview]
Message-ID: <4030979.D58EjbuuB0@flexo> (raw)
In-Reply-To: <20120717142926.05c0c17f@skate>
On Tuesday 17 July 2012 14:29:26 Thomas Petazzoni wrote:
> Le Tue, 17 Jul 2012 13:13:03 +0100,
> Ian Molton <ian.molton@codethink.co.uk> a ?crit :
>
> > Unless I'm misunderstanding it, thats not quite what I need -
> > although I should probably have made my hack depend on it.
> >
> > I'm using a uImage; The prepending needs to happen to the zImage /
> > Image.
>
> What I typically do is generate a zImage, do the appending, and then
> generate the uImage manually with mkimage. But I agree it could be
> useful to have a 'make uImage.myboard' target which would happen the
> myboard.dtb before preparing the uImage.
Appending a given device tree blob to a zImage is something that should be
solved outside of the kernel build imho.
Since your bootloader is already "non-cooperative" wrt DTBs, you need to
provide a specific uImage (zImage + dtb) for it.
I do not think the kernel build should try to generate as many zImages as
there dtb files, nor any other combination, this really is distribution
specific.
--
Florian
next prev parent reply other threads:[~2012-07-17 12:41 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 11:55 Device tree Ian Molton
2012-07-17 12:01 ` Thomas Petazzoni
2012-07-17 12:13 ` Ian Molton
2012-07-17 12:29 ` Thomas Petazzoni
2012-07-17 12:41 ` Florian Fainelli [this message]
2012-07-17 13:32 ` Thomas Petazzoni
2012-07-17 12:32 ` Josh Coombs
2012-07-17 13:07 ` Ian Molton
2012-07-17 13:25 ` Ben Dooks
2012-07-17 13:52 ` Rob Herring
2012-07-17 13:56 ` Ben Dooks
2012-07-17 14:02 ` Florian Fainelli
2012-07-17 14:55 ` Ian Molton
2012-07-17 21:18 ` Nicolas Pitre
2012-07-18 7:51 ` Ian Molton
2012-07-18 13:42 ` Nicolas Pitre
2012-07-19 9:07 ` Ian Molton
2012-07-19 21:32 ` Nicolas Pitre
2012-07-23 13:10 ` Mark Brown
2012-07-17 14:05 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2016-10-25 6:21 Device Tree Madhu K
2016-10-25 7:32 ` Laurent Navet
2016-10-25 7:39 ` Valdis.Kletnieks at vt.edu
2016-10-25 10:12 ` Joel
2016-10-25 10:16 ` Madhu K
2016-10-25 15:43 ` Valdis.Kletnieks at vt.edu
2008-09-29 6:24 Sébastien Chrétien
2008-09-29 8:25 ` Sergei Shtylyov
2008-09-30 15:22 ` Matt Sealey
2008-09-30 22:30 ` Gerald Van Baren
2008-09-30 23:08 ` Matt Sealey
2008-10-01 3:24 ` Benjamin Herrenschmidt
2008-10-01 13:09 ` Matt Sealey
2008-10-29 21:04 ` Sébastien Chrétien
2008-09-29 8:25 ` Sergei Shtylyov
2008-09-29 8:51 ` Benjamin Herrenschmidt
2008-09-09 15:43 Georg Schardt
2008-09-09 17:33 ` Josh Boyer
2008-09-09 18:11 ` John Linn
2008-09-09 18:19 ` Georg Schardt
2008-09-09 18:24 ` John Linn
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=4030979.D58EjbuuB0@flexo \
--to=florian@openwrt.org \
--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.