[PATCH 6/6] bootwrapper: cuboot for 83xx

[Scott Wood]

On Sat, Mar 24, 2007 at 10:37:12AM +1100, David Gibson wrote:
> Is there any reasonable way we can determine the memory size early
> enough for the zImage to relocate itself to (approximately) the top of
> RAM first thing?

We can with cuboot (and it's at the beginning of the bd_t, so it's not
affected by the ifdef mess), but some platforms might require accessing
the device tree to get that information.

> Or we could get the wrapper script to base the link/load address on
> the vmlinux size.

That'd be nice.

> > I'm not sure that it's true that only in-tree device trees would be used
> > -- I can imagine customers having old firmware on custom boards that
> > would like to upgrade the kernel, but do not want to upgrade the
> > firmware.
> 
> Um.. since the zImage's tree comes from the kernel, what does
> upgrading the firmware have to do with it?

My point was simply that it's not just the reference boards with
in-kernel dts files that this would be useful on.  Thus, it makes sense
to allow out-of-tree dts files.

> > I'd be happy to see the name be changed to just be "/soc", though it
> > would require u-boot changes.
> 
> Err.. why?

So we don't have to partition the dts files into "works with cuimage" and
"works with dt-aware u-boot".  U-boot has hardcoded references to the soc
node with model number.

-Scott