From: Scott Wood <scottwood@freescale.com>
To: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
Cc: John Linn <linnj@xilinx.com>,
paulus@samba.org, linuxppc-dev@ozlabs.com,
petermendham@computing.dundee.ac.uk
Subject: Re: [PATCH] powerpc/bootwrapper: Add documentation of boot wrappertargets
Date: Thu, 26 Jun 2008 15:22:32 -0500 [thread overview]
Message-ID: <4863FA88.1010708@freescale.com> (raw)
In-Reply-To: <20080626201643.D01221788058@mail223-wa4.bigfish.com>
Stephen Neuendorffer wrote:
>> cuImage is for boards running an older U-Boot that does not understand
>> device trees.
>
> Forgive my ignorance here, but what specifically does this imply? As
> far as I can tell, generally speaking, some of the board-specific
> information is passed into the boot wrapper, which then stuffs it into
> the device tree.
It implies that the binary is in uImage format, targets older u-boot (as
opposed to some other bootloader entirely, which might be targeted with
a dtbImage -- see adder875, for example), and has a device tree embedded.
>> uImage is for device-tree aware U-Boot versions
>
> And this differs from above because it gets a device tree passed in,
> which uboot has already stuffed correctly.
Yes.
>> dtbImage is used for boards that can take an ELF zImage, but still
> need
>> a dtb provided.
>>
>> simpleImage, not sure here.
>
> So both of these are elfs... but how do they differ? Is it only in how
> the right head.s file gets picked up?
Neither is necessarily an ELF. The only simpleboot target I see is a
flat binary, as are some of the dtbImage targets (adder875, ep88xc,
ep405, etc). simpleboot is more of a platform than an image type; it's
a platform that assumes nothing about the firmware that loaded it, and
gets all information from the embedded device tree.
-Scott
next prev parent reply other threads:[~2008-06-26 20:22 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
2008-06-26 20:16 ` [PATCH] powerpc/bootwrapper: Add documentation of boot wrappertargets Stephen Neuendorffer
2008-06-26 20:22 ` Scott Wood [this message]
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=4863FA88.1010708@freescale.com \
--to=scottwood@freescale.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 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).