Re: [PATCH 2/4] sparc: break out some prom device-tree building code out into drivers/of

[Grant Likely]

On Tue, Jul 6, 2010 at 1:16 AM, David Miller <davem@xxxxxxxxxxxxx> wrote:
> From: Grant Likely <grant.likely@xxxxxxxxxxxx>
> Date: Tue, 6 Jul 2010 01:00:06 -0600
>
>> I'm curious... what are your plans here?  Will you be keeping OF alive
>> between kexec()?  Will the new kernel get the entire device tree from
>> fdt, or will it still be talking to OF?  How will the fdt fragments as
>> Andres described above fit into sparc kexec (as opposed to generating
>> one big tree as in his first option)?
>
> On certain sparc64 systems, I have to stop making PROM calls early
> in the boot right after I fetch the device tree into the kernel.
>
> So yes for a kexec() I'll have to pass an fdt or similar to the
> child kernel.
>
> It could be a big linear fdt buffer, or fragments, it really doesn't
> matter all that much actually.

Okay.  There is already support for getting the tree out of the kernel
and into fdt form via procfs.  Userspace can also modify it before
sending it back to kexec().  This will be easy no matter which
approach Andres uses.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/