CONFIG_GENERIC_PPC32
Quoted 1 line · Benjamin Herrenschmidt
Let's do it first in 2.5, we can backport it once we are satisfied
Bleah. 2.5 == never to me. It doesn't help me with my goal of getting support for my boards in 2.4. I work on stable kernels and not development ones because I'm not a Linux developer, I'm just a HW engineer trying to make Linux (existing stable one) support my boards at least as well as it does those from my competitors (IBM, Sun, etc).
I guess I'll just have to convince Debian to make a package from linuxppc_2_4_alt to support HEC PPCStar machines and show all these exchanges as evidence that the PPC MAINTAINERS are not intent on allowing new machine support into 2.4 any time soon.
Quoted 4 lines
Well.. you forget pmac here ;)
The problem is that pmac has it's own serial HW with a different driver, but still may need serial.o for PCI serial cards or pcmcia modems.
But then a PMac doesn't need anything in rs_table!
If in addition to PMacs a CONFIG_GENERIC_PPC32 kernel supports other machines with serial consoles, the serial driver must be compiled in. If no machines other than PMac are selected, you can compile without the serial driver in there as the PMac port won't care about rs_table and won't call early_serial_setup. Then if you load it as a module, you'll have no fixed ports will get all PCI, PCMCIA, etc. ones, which is exactly what you need here.
So I don't see a problem.
MS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Quoted 9 lines · Michael Sokolov
Quoted 1 line · Benjamin Herrenschmidt
Let's do it first in 2.5, we can backport it once we are satisfied
Bleah. 2.5 == never to me. It doesn't help me with my goal of getting support for my boards in 2.4. I work on stable kernels and not development ones because I'm not a Linux developer, I'm just a HW engineer trying to make Linux (existing stable one) support my boards at least as well as it does those from my competitors (IBM, Sun, etc).
Quoted 4 lines
I guess I'll just have to convince Debian to make a package from
linuxppc_2_4_altto support HEC PPCStar machines and show all these exchanges as evidence that the PPCMAINTAINERSare not intent on allowing new machine support into 2.4 any time soon.
Please note that most probably Marcelo won't accept new machine support into 2.4.x neither, unless it's a backport of 2.5.x and it has proven to be stable.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Quoted 6 lines
I guess I'll just have to convince Debian to make a package from
linuxppc_2_4_altto support HEC PPCStar machines and show all these exchanges as evidence that the PPCMAINTAINERSare not intent on allowing new machine support into 2.4 any time soon.
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.
Quoted 6 lines
Quoted 4 lines
Well.. you forget pmac here ;)
The problem is that pmac has it's own serial HW with a different driver, but still may need serial.o for PCI serial cards or pcmcia modems.
But then a PMac doesn't need anything in
rs_table!
But a pmac/prep/chrp kernel may.
Quoted 9 lines
If in addition to PMacs a
CONFIG_GENERIC_PPC32kernel supports other machines with serial consoles, the serial driver must be compiled in. If no machines other than PMac are selected, you can compile without the serial driver in there as the PMac port won't care aboutrs_tableand won't callearly_serial_setup. Then if you load it as a module, you'll have no fixed ports
will get all PCI, PCMCIA, etc. ones, which is exactly what you need here.So I don't see a problem.
Not having it as a module may prevent pcmcia modems from working.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/