From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: linux-kernel@vger.kernel.org
Subject: Re: seems to be impossible to disable CONFIG_SERIAL [2.6.7]
Date: Fri, 10 Sep 2004 14:07:33 +0100 [thread overview]
Message-ID: <20040910130733.GI14060@lkcl.net> (raw)
In-Reply-To: <20040910133545.E22599@flint.arm.linux.org.uk>
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".
l.
--
--
Truth, honesty and respect are rare commodities that all spring from
the same well: Love. If you love yourself and everyone and everything
around you, funnily and coincidentally enough, life gets a lot better.
--
<a href="http://lkcl.net"> lkcl.net </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />
next prev parent reply other threads:[~2004-09-10 12:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 11:08 seems to be impossible to disable CONFIG_SERIAL [2.6.7] Luke Kenneth Casson Leighton
2004-09-10 11:09 ` Russell King
2004-09-10 12:20 ` Luke Kenneth Casson Leighton
2004-09-10 12:35 ` Russell King
2004-09-10 12:59 ` Roman Zippel
2004-09-10 14:00 ` Alan Cox
2004-09-10 13:07 ` Luke Kenneth Casson Leighton [this message]
2004-09-10 18:12 ` Bill Davidsen
2004-09-10 20:55 ` Kyle Moffett
2004-09-15 14:56 ` Bill Davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040910130733.GI14060@lkcl.net \
--to=lkcl@lkcl.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox