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

Grant Likely
2010-07-06T07:00:29Z

On Mon, Jul 5, 2010 at 8:22 PM, David Miller <davem@davemloft.net> wrote:
> From: Andres Salomon <dilinger@queued.net>
> Date: Wed, 7 Jul 2010 04:07:34 +0000
>
>>  - For the pdt, calling into the prom once for each property/node to
>>    create a fdt, and then unflattening it.  This is better than the
>>    previous option, but I don't think the prom->fdt code will be very
>>    nice.
>
> I'll need this on sparc64 at some point to support kexec() anyways.
>
> So at least for sparc you can assume that a something-->fdt translator
> is going to exist at some point in the future regardless of what
> happens here.

Hi David,

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)?

Cheers,
g.

--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.