[RFC] arch/ppc/boot/simple/embed_boot.c : Merging all keyvals parsing code

[Jon Loeliger]

On Tue, 2006-01-31 at 14:31, Peter Korsgaard wrote:
> >>>>> "Tom" == Tom Rini <trini at kernel.crashing.org> writes:
> 
>  Tom> I would suggest either Linus' current git tree or 2.6.16-rc1 if
>  Tom> you don't use git.  But please bear in mind that since this is a
>  Tom> new feature (a new board) it won't be submitted to Linus' tree
>  Tom> until 2.6.17-rc1 opens up (and if in that time, it becomes much
>  Tom> easier to put this board under arch/powerpc it should be done
>  Tom> under there, instead).
> 
> I only recently moved from 2.4 to 2.6, so this may be a FAQ, but a
> quick googling around didn't find anything.
> 
> What is this arch/ppc -> arch/powerpc about? Some kind of
> consolidation of ppc and ppc64?

Exactly.

> What's the reason behind it

Eliminate duplicate code.  Share good code.
Improved modularity.  Leverage.  All the Good Stuff (tm).
Eliminate the bd_t mess.  You know.

> and what kind of time frame are we talking about?

In progress now.  All of the PPC64 ports are now officially
part of the "powerpc" arch.  There are two published PPC32
ports (MPC8349SYS and MPC8540ADS) that have been posted to
the list as being "merged" into the powerpc arch.  They are
still evolving a bit, though.

>  Is it related to the bd_t ->
> flattened OF tree change?

Yes.  New World Order says all arch/powerpc ports will 
use a common flat dev tree interface from boot loaders
unless honest OF is available.  The bd_t is obsolete.

> Could someone post a few pointers to more information? 

Read the "booting without open firmware" spec recently
patched from the DTC code tree to the linux doc directory
on the PPC64 list by Dave Gibson.

Read the Device Tree Compiler code itself too.

jdl