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

David Miller
2010-07-06T02:22:09Z

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.