CONFIG_GENERIC_PPC32

[benh at kernel.crashing.org]

>> Don't get to conclusions so fast. We have already a whole bunch of new
>> machines support pending in _devel that has to be merged, and that will
>> happen after 2.4.19. Things aren't fast on a stable kernel, but that's
>> the way it should be.
>
>Then why won't you accept my PPCStar port into 2_4_devel?

I didn't say I didn't accept it. Paulus is the one to ultimately decide
about that though, but I understand if he wants to put a hold on new
boards until at least _devel gets merged into 2.4

>> Not having it as a module may prevent pcmcia modems from working.
>
>OK, now I see the fundamental conflict of interest. Your machines and mine
>can't coexist in the same kernel I guess then because mine can't work
with the
>serial driver as a module (because it's the system console) and yours can't
>work with it compiled in because of PCMCIA. Let's have separate
>CONFIG_CHRP_PMAC_PREP and CONFIG_HEC_PPCSTAR then.

No, let's fix the brain-damaged serial driver ;)

Ben.


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