On Wed, Jun 08, 2005 at 01:06:37PM +1000, Benjamin Herrenschmidt wrote:
[snip]
> Regarding code in arch/ppc*, I'm not sure what the right approach would
> be. I'd say first copy things around, and we'll what we end up with.
How about we just do:
obj-y += ../../ppc64/kernel/flat_tree.o
or so like x
On Wed, 2005-06-15 at 14:00 -0500, Jon Loeliger wrote:
> On Tue, 2005-06-07 at 22:06, Benjamin Herrenschmidt wrote:
>
> > It's basically used to extract some infos directly from the flattened
> > tree in order to construct the LMB list (list of memory blocks,
> > equivalent of ppc32's mem_pieces),
On Tue, 2005-06-07 at 22:06, Benjamin Herrenschmidt wrote:
> It's basically used to extract some infos directly from the flattened
> tree in order to construct the LMB list (list of memory blocks,
> equivalent of ppc32's mem_pieces),
OK. So the unflattenting process requires a small amount
of
On Fri, 2005-06-03 at 12:19 -0500, Jon Loeliger wrote:
> Ben and Folks,
Hi Jon !
> I've read through ppc64/kernel/prom.c and done some minor
> call-chain analysis rooted at the two functions:
> early_init_devtree()
> unflatten_device_tree()
> as they are apparently the only two referenced
Ben and Folks,
I've read through ppc64/kernel/prom.c and done some minor
call-chain analysis rooted at the two functions:
early_init_devtree()
unflatten_device_tree()
as they are apparently the only two referenced in the
initial early boot up process.
My notion was to take the portion of
