From: David Gibson <david@gibson.dropbear.id.au>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 6/6] bootwrapper: cuboot for 83xx
Date: Wed, 4 Apr 2007 16:38:34 +1000 [thread overview]
Message-ID: <20070404063834.GA26616@localhost.localdomain> (raw)
In-Reply-To: <20070404020629.GA2453@mag.az.mvista.com>
On Tue, Apr 03, 2007 at 07:06:29PM -0700, Mark A. Greer wrote:
> 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
> somehow.
Sure. The wrapper already does platform dependent things, so I was
assuming it would only do this for some platforms.
> > > > 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.
Sorry, I should clarify. In the context of libfdt, I was thinking
*read* access to the fdt can happen at any point - right from
platform_init(). ft_open() would mark the point at which write access
to the tree can begin.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-04-04 6:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 19:46 [PATCH 0/6] bootwrapper/cuboot Scott Wood
2007-03-22 19:49 ` [PATCH 1/6] bootwrapper: Add dt_xlate_reg(), and use it to find serial registers Scott Wood
2007-03-22 19:49 ` [PATCH 2/6] bootwrapper: Add ppcboot.h Scott Wood
2007-03-22 19:49 ` [PATCH 3/6] bootwrapper: Add support for cuboot platforms Scott Wood
2007-03-23 5:25 ` David Gibson
2007-03-22 19:49 ` [PATCH 4/6] bootwrapper: Add CONFIG_DEVICE_TREE Scott Wood
2007-03-22 19:49 ` [PATCH 5/6] bootwrapper: Add a cuImage target Scott Wood
2007-03-23 5:40 ` David Gibson
2007-03-23 15:18 ` Scott Wood
2007-03-23 23:39 ` David Gibson
2007-03-22 19:49 ` [PATCH 6/6] bootwrapper: cuboot for 83xx Scott Wood
2007-03-23 5:54 ` David Gibson
2007-03-23 15:30 ` Scott Wood
2007-03-23 23:37 ` David Gibson
2007-03-26 15:53 ` Scott Wood
2007-04-04 2:06 ` Mark A. Greer
2007-04-04 6:38 ` David Gibson [this message]
2007-04-04 16:01 ` Mark A. Greer
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=20070404063834.GA26616@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=mgreer@mvista.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).