On Fri, Sep 10, 2004 at 01:35:45PM +0100, Russell King wrote:
On Fri, Sep 10, 2004 at 01:20:59PM +0100, Luke Kenneth Casson Leighton wrote:
On Fri, Sep 10, 2004 at 12:09:50PM +0100, Russell King wrote:
On Fri, Sep 10, 2004 at 12:08:19PM +0100, Luke Kenneth Casson Leighton wrote:
hi,
has anyone noticed that it's impossible (without hacking) to remove
CONFIG_SERIAL?
remove the entries or set all SERIAL config entries to "n"...
hit make...
CONFIG_SERIAL_8250 gets set to "m", CONFIG_SERIAL gets set to "y"!
seeerrrriiialllll muuuusssstttt dieeeeeee kill kill kill.
No idea - you've given very little information to go on. I doubt
you're building an x86 kernel... Mind giving some clues and maybe
a copy of your .config file?
x86 kernel, debian default config with legacy stuff like
sure.
Ok, so it _isn't_ CONFIG_SERIAL at all. Grumble.
Anyway, CONFIG_SERIAL_8250 gets set to 'm' because:
$ find . -name 'Kconfig*' | xargs grep 'select SERIAL_8250' -B5
./drivers/char/Kconfig-source "drivers/char/pcmcia/Kconfig"
./drivers/char/Kconfig-
./drivers/char/Kconfig-config MWAVE
./drivers/char/Kconfig- tristate "ACP Modem (Mwave) support"
./drivers/char/Kconfig- depends on X86
./drivers/char/Kconfig: select SERIAL_8250
and you have CONFIG_MWAVE is set to 'm'.
oh, do i? looovely, what's one of those when it's at home?
it would appear that the "select ..." thing is what's causing the
nightmares: it forces options to be enabled without informing the user,
and without the user being able to do it the other way round:
say "i don't want CONFIG_SERIAL_8250 and therefore any option depending
on it can bugger off".