[PATCH 6/6] bootwrapper: cuboot for 83xx
Mark A. Greer
mgreer at mvista.com
Wed Apr 4 12:06:29 EST 2007
On Sat, Mar 24, 2007 at 10:37:12AM +1100, David Gibson wrote:
> On Fri, Mar 23, 2007 at 10:30:56AM -0500, Scott Wood wrote:
> > On Fri, Mar 23, 2007 at 04:54:42PM +1100, David Gibson wrote:
> > > I don't think you should need a vmlinux_alloc for this platform.
> > Without it, the kernel has to fit in 4MiB. As others pointed out, that
> > can be too small if an initramfs is used. Unlike 8xx (which was what
> > caused me to stick the kernel at 0 in previous patches), 83xx platforms
> > should have plenty of memory above the wrapper.
> Or we could get the wrapper script to base the link/load address on
> the vmlinux size.
That might be handy for some but it won't work for everyone. Some
platforms require a specific link/load address. We can provide what
you said as a default but allow it to be overridden by platform code
> > > The more complicated reason is that looking ahead to when we're using
> > > libfdt instead of flatdevtree.c, we may need an extra step that
> > > prepares the device tree for read/write access (with libfdt, an
> > > fdt_open_into()). That won't happen until after platform_init(), but
> > > will be before .fixups().
> > OK.
> Actually, to be clearer here: this reason actually degenerates to the
> first; I want the "ft_open" step to go after console_open so we can
> get error messages from it.
The problem is, the console device is specified in the dt so you have
to ft_open before you console_open.
More information about the Linuxppc-dev