CONFIG_GENERIC_PPC32

[Benjamin Herrenschmidt]

>On Sat, 6 Apr 2002, Benjamin Herrenschmidt wrote:
>> I've looked at the patch in the meantime and it makes much sense. I want
>> to do something around those lines:
>>
>>  - Completely rip off CONFIG_ALL_PPC in favor of CONFIG_GENERIC_PPC32
>>  - Each board model has it's own CONFIG_xxx entry (like Michael patch),
>>    which means adding "back" CONFIG_PMAC, CONFIG_CHRP, CONFIG_PREP, but
>>    those will only control which set of .c file will get in the makefile
>>    and the toplevel switch/case on platform_init. That is you will be able
>>    to select an arbitrary set of boards.
>
>Good, starts to look like m68k again, where you always were able to compile a
>generic kernel (except for Sun-3 (not 3x) due to the different MMU)!
>Now start moving platform specific files to arch/ppc/$platform/ again. Dan is
>right, we're running in circles :-)

No, we aren't ;)

In some way, all those new board brought us back to the pre-CONFIG_ALL_PPC
days since they all have their own config option and can't live in a
generic kernel. Mostly for no reason except maybe detecting the board
at boot time (which can be done in the wrapper now if there is no other
way).

The other way, iirc, making the generic (CONFIG_ALL_PPC) kernel from
split pmac/chrp/prep was necessary to get the non-platform specific code
really non-platform specific (at that time, we had the "common" irq, pci
etc... code diff'ing between platforms or #ifdef'ed in places).

So we aren't circling here. We are slowly moving toward an arch where the
common code is really common and no crippled with platform ifdefs, and
a platform is just a set of functions behind ppc_md along with appropriate
drivers beeing in the Makefile. It's a logical step to do the (few) Makefile
and Config.in work to make those individual platforms be selectable
in arbitrary sets.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/