From: Josh Boyer <jwboyer@gmail.com>
To: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
Cc: John Linn <linnj@xilinx.com>,
petermendham@computing.dundee.ac.uk, linuxppc-dev@ozlabs.com,
paulus@samba.org
Subject: RE: [PATCH] powerpc/bootwrapper: Add documentation of boot wrapper targets
Date: Thu, 26 Jun 2008 15:07:18 -0400 [thread overview]
Message-ID: <1214507238.7698.3.camel@weaponx> (raw)
In-Reply-To: <20080626164842.1D3AB1358053@mail15-sin.bigfish.com>
On Thu, 2008-06-26 at 09:48 -0700, Stephen Neuendorffer wrote:
> My unanswered questions:
>
> 1) Why are there 4 different types of targets that embed a device tree?
> I assume they differ in how they are started loaded, but (unfortunately)
> the names are meaningless (With the exception of cuImage, which is only
> cryptic.. :) If I'm adding support for a new board, which should I use?
They are all needed to deal with different firmwares.
treeImage is for OpenBIOS based boards (Ebony, Walnut, some boards
running PIBS can also use this). This firmware requires a special
header on the image file.
cuImage is for boards running an older U-Boot that does not understand
device trees.
uImage is for device-tree aware U-Boot versions
dtbImage is used for boards that can take an ELF zImage, but still need
a dtb provided.
simpleImage, not sure here.
josh
next prev parent reply other threads:[~2008-06-26 19:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 20:21 [PATCH] powerpc/bootwrapper: Add documentation of boot wrapper targets Grant Likely
2008-06-26 5:02 ` Grant Likely
2008-06-26 13:35 ` John Linn
2008-06-26 16:48 ` Stephen Neuendorffer
2008-06-26 17:21 ` Peter Mendham
2008-06-26 19:07 ` Josh Boyer [this message]
2008-06-26 20:16 ` [PATCH] powerpc/bootwrapper: Add documentation of boot wrappertargets Stephen Neuendorffer
2008-06-26 20:22 ` Scott Wood
2008-06-28 4:22 ` Grant Likely
2008-06-29 21:30 ` Stephen Neuendorffer
2008-06-27 17:49 ` [PATCH] powerpc/bootwrapper: Add documentation of boot wrapper targets Scott Wood
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=1214507238.7698.3.camel@weaponx \
--to=jwboyer@gmail.com \
--cc=linnj@xilinx.com \
--cc=linuxppc-dev@ozlabs.com \
--cc=paulus@samba.org \
--cc=petermendham@computing.dundee.ac.uk \
--cc=stephen.neuendorffer@xilinx.com \
/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.