From: Pavel Machek <pavel@suse.cz>
To: Christoph Hellwig <hch@infradead.org>, Andi Kleen <ak@muc.de>,
linux-kernel@vger.kernel.org, akpm@digeo.com, vojtech@suse.cz
Subject: Re: [PATCH] Making keyboard/mouse drivers dependent on CONFIG_EMBEDDED
Date: Sat, 7 Jun 2003 22:43:40 +0200 [thread overview]
Message-ID: <20030607204340.GC667@elf.ucw.cz> (raw)
In-Reply-To: <20030607082651.A18894@infradead.org>
Hi!
> > I finally got sick of seeing bug reports from people who did not enable
> > CONFIG_VT or forgot to enable the obscure options for the keyboard
> > driver. This is especially a big problem for people who do make oldconfig
> > with a 2.4 configuration, but seems to happen in general often.
> > I also included the PS/2 mouse driver. It is small enough and a useful
> > fallback on any PC.
> >
> > This patch wraps all this for i386/amd64 in CONFIG_EMBEDDED. If
> > CONFIG_EMBEDDED is not defined they are not visible and always enabled.
>
> This sounds like a bad idea. many modern PCs only have usb keyboard/mouse
> these days. Having them in defconfig is fine but we shouldn't obsfucate
> the kernel config due to user stupidity.
Its more like "make oldconfig" limitation, IIRC. If you have some old
config, it ignores defconfig and suggests you N for new options. And
yes people were hitting that.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-06-07 20:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-07 6:34 [PATCH] Making keyboard/mouse drivers dependent on CONFIG_EMBEDDED Andi Kleen
2003-06-07 6:45 ` Aaron Lehmann
2003-06-07 17:02 ` Roman Zippel
2003-06-07 6:49 ` YOSHIFUJI Hideaki / 吉藤英明
2003-06-07 18:40 ` Andi Kleen
2003-06-07 20:18 ` Ryan Anderson
2003-06-07 7:26 ` Christoph Hellwig
2003-06-07 20:43 ` Pavel Machek [this message]
2003-06-08 0:43 ` Arador
2003-06-07 9:59 ` Vojtech Pavlik
2003-06-07 18:44 ` Andi Kleen
2003-06-07 20:27 ` Vojtech Pavlik
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=20030607204340.GC667@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@muc.de \
--cc=akpm@digeo.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).