From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: Device tree.
Date: Tue, 17 Jul 2012 15:32:55 +0200 [thread overview]
Message-ID: <20120717153255.2d171eac@skate> (raw)
In-Reply-To: <4030979.D58EjbuuB0@flexo>
Le Tue, 17 Jul 2012 14:41:35 +0200,
Florian Fainelli <florian@openwrt.org> a ?crit :
> > 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.
Well, both PowerPC and Microblaze, and apparently C6X, have some sort
of <imageFormat>.<dtbName> make target:
$ make ARCH=microblaze help
[...]
simpleImage.<dt> - ELF image with /boot/dts/<dt>.dts linked in
- stripped elf with fdt blob
simpleImage.<dt>.unstrip - full ELF image with fdt blob
$ make ARCH=powerpc help
[...]
cuImage.<dt> - Backwards compatible U-Boot image for older
versions which do not support device trees
dtbImage.<dt> - zImage with an embedded device tree blob
simpleImage.<dt> - Firmware independent image.
treeImage.<dt> - Support for older IBM 4xx firmware (not U-Boot)
$ make ARCH=c6x help
[...]
dtbImage.<dt> - ELF image with /boot/dts/<dt>.dts linked in
- stripped elf with fdt blob
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-17 13:32 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
2012-07-17 13:32 ` Thomas Petazzoni [this message]
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=20120717153255.2d171eac@skate \
--to=thomas.petazzoni@free-electrons.com \
--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.