On Wed, Jun 25, 2008 at 01:21:04PM -0700, Grant Likely wrote:
> + zImage.%: Image usable by OpenFirmware. Image expects firmware
> + to provide the device tree using OpenFirmware
> + interfaces. Typically general purpose hardware uses
> +
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 cuImag
Thanks for this documentation - I found it very illuminating. My
question was going to be similar to Stephen's in that I don't find it
clear which of the images with an embedded device tree I should be
using. This is all in contrast to the Xilinx git tree where I just use
zImage with a config
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, wh
Thanks Grant, that's a great start for helping us to better understand
the bootwrapper.
The wrapper is somewhat complex and hard to get your head around, or at
least my head ;).
-- John
-Original Message-
From: Grant Likely [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 25, 2008 2:21 P
Oops, sent to the wrong address for the mailing list...
From: Grant Likely <[EMAIL PROTECTED]>
There have been many questions on and off the mailing list about how
exactly the bootwrapper is used for embedded targets. Add some
documentation and help text to try and clarify the system.
Signed-of
