* Re: Petition against kernel configuration options madness...
2002-11-03 19:07 ` Vojtech Pavlik
@ 2002-11-03 19:37 ` Petr Baudis
2002-11-03 20:13 ` Vojtech Pavlik
2002-11-03 20:38 ` Arador
` (4 subsequent siblings)
5 siblings, 1 reply; 29+ messages in thread
From: Petr Baudis @ 2002-11-03 19:37 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: Jeff Garzik, Jos Hulzink, linux-kernel
Dear diary, on Sun, Nov 03, 2002 at 08:07:05PM CET, I got a letter,
where Vojtech Pavlik <vojtech@suse.cz> told me, that...
> On Sun, Nov 03, 2002 at 12:52:48PM -0500, Jeff Garzik wrote:
> > Jos Hulzink wrote:
> >
> > >It took me about an hour to find out why my keyboard didn't work in 2.5.45.
> > >Well... after all it seemed that I need to enable 4 ! options inside the
> > >input configuration, just to get my default, nothing special PS/2 keyboard up
> > >and running. Oh, and I didn't even have my not so fancy boring default PS/2
> > >mouse configured then. Guys, being able to configure everything is nice, but
> > >with the 2.5 kernel, things are definitely getting out of control IMHO.
> > >
> > >
> >
> > This is potentially becoming a FAQ... I ran into this too, as did
> > several people in the office. People who compile custom kernels seem to
> > run into this when they first jump into 2.5.x. AT Keyboard support is
> > definitely buried :/
> >
> > Unfortunately I don't have any concrete suggestions for Vojtech (input
> > subsystem maintainer), just a request that it becomes easier and more
> > obvious how to configure the keyboard and mouse that is found on > 90%
> > of all Linux users computers [IMO]...
>
> Too bad you don't have any suggestions. I completely agree this should
> be simplified, while I wouldn't be happy to lose the possibility of not
> compiling AT keyboard support in.
Well, why can't it be enabled by default? Other options are as well, and it's
IMHO sane to enable keyboard and mice support by default. It should clear up
the initial confusion as well.
I think that these options should be enabled by default:
[Userland interfaces]
Mouse interface
Legacy /dev/psaux (?)
(I suggest to make this non-default in 2.7, but maybe
we want shorter transition period?)
[Input I/O drivers]
Serial i/o support
i8042
Serial port line discipline
[Input device drivers]
Keyboards
AT keyboard support
Mice
Serial mouse (?)
(..or maybe not, this is really not so common as PS/2
lately)
PS/2 mouse
I think that those are absolute minimum and if anyone will want to have any of
these explicitly off, he's more likely to know where to turn it off, rather
than vice versa.
--
Petr "Pasky" Baudis
.
This host is a black hole at HTTP wavelengths. GETs go in, and nothing
comes out, not even Hawking radiation.
-- Graaagh the Mighty on rec.games.roguelike.angband
.
Public PGP key && geekcode && homepage: http://pasky.ji.cz/~pasky/
^ permalink raw reply [flat|nested] 29+ messages in thread* Re: Petition against kernel configuration options madness...
2002-11-03 19:37 ` Petr Baudis
@ 2002-11-03 20:13 ` Vojtech Pavlik
2002-11-03 22:20 ` Petr Baudis
2002-11-03 22:25 ` Petition against kernel configuration options madness Jos Hulzink
0 siblings, 2 replies; 29+ messages in thread
From: Vojtech Pavlik @ 2002-11-03 20:13 UTC (permalink / raw)
To: Vojtech Pavlik, Jeff Garzik, Jos Hulzink, linux-kernel
On Sun, Nov 03, 2002 at 08:37:34PM +0100, Petr Baudis wrote:
> Dear diary, on Sun, Nov 03, 2002 at 08:07:05PM CET, I got a letter,
> where Vojtech Pavlik <vojtech@suse.cz> told me, that...
> > On Sun, Nov 03, 2002 at 12:52:48PM -0500, Jeff Garzik wrote:
> > > Jos Hulzink wrote:
> > >
> > > >It took me about an hour to find out why my keyboard didn't work in 2.5.45.
> > > >Well... after all it seemed that I need to enable 4 ! options inside the
> > > >input configuration, just to get my default, nothing special PS/2 keyboard up
> > > >and running. Oh, and I didn't even have my not so fancy boring default PS/2
> > > >mouse configured then. Guys, being able to configure everything is nice, but
> > > >with the 2.5 kernel, things are definitely getting out of control IMHO.
> > > >
> > > >
> > >
> > > This is potentially becoming a FAQ... I ran into this too, as did
> > > several people in the office. People who compile custom kernels seem to
> > > run into this when they first jump into 2.5.x. AT Keyboard support is
> > > definitely buried :/
> > >
> > > Unfortunately I don't have any concrete suggestions for Vojtech (input
> > > subsystem maintainer), just a request that it becomes easier and more
> > > obvious how to configure the keyboard and mouse that is found on > 90%
> > > of all Linux users computers [IMO]...
> >
> > Too bad you don't have any suggestions. I completely agree this should
> > be simplified, while I wouldn't be happy to lose the possibility of not
> > compiling AT keyboard support in.
>
> Well, why can't it be enabled by default? Other options are as well, and it's
> IMHO sane to enable keyboard and mice support by default. It should clear up
> the initial confusion as well.
All the needed options ARE enabled by default. (check arch/i386/defconfig)
> I think that those are absolute minimum and if anyone will want to have any of
> these explicitly off, he's more likely to know where to turn it off, rather
> than vice versa.
--
Vojtech Pavlik
SuSE Labs
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: Petition against kernel configuration options madness...
2002-11-03 20:13 ` Vojtech Pavlik
@ 2002-11-03 22:20 ` Petr Baudis
2002-11-03 22:32 ` [PATCH] Sane defaults for the input layer configuration Petr Baudis
2002-11-03 22:25 ` Petition against kernel configuration options madness Jos Hulzink
1 sibling, 1 reply; 29+ messages in thread
From: Petr Baudis @ 2002-11-03 22:20 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: Jeff Garzik, Jos Hulzink, linux-kernel
Dear diary, on Sun, Nov 03, 2002 at 09:13:08PM CET, I got a letter,
where Vojtech Pavlik <vojtech@suse.cz> told me, that...
> On Sun, Nov 03, 2002 at 08:37:34PM +0100, Petr Baudis wrote:
> > Dear diary, on Sun, Nov 03, 2002 at 08:07:05PM CET, I got a letter,
> > where Vojtech Pavlik <vojtech@suse.cz> told me, that...
> > > Too bad you don't have any suggestions. I completely agree this should
> > > be simplified, while I wouldn't be happy to lose the possibility of not
> > > compiling AT keyboard support in.
> >
> > Well, why can't it be enabled by default? Other options are as well, and it's
> > IMHO sane to enable keyboard and mice support by default. It should clear up
> > the initial confusion as well.
>
> All the needed options ARE enabled by default. (check arch/i386/defconfig)
Yes, but if this will be in the Kconfig as well (I mean adding "default y"
lines, I can make a patch, if there's a desire), it will be offered as default
even when doing make oldconfig, which is what most of the people is going to do
(not make defconfig, most of people doesn't even know it exists and the rest
probably wants to configure 2.5 based on their 2.4 configuration anyway).
--
Petr "Pasky" Baudis
.
This host is a black hole at HTTP wavelengths. GETs go in, and nothing
comes out, not even Hawking radiation.
-- Graaagh the Mighty on rec.games.roguelike.angband
.
Public PGP key && geekcode && homepage: http://pasky.ji.cz/~pasky/
^ permalink raw reply [flat|nested] 29+ messages in thread* [PATCH] Sane defaults for the input layer configuration
2002-11-03 22:20 ` Petr Baudis
@ 2002-11-03 22:32 ` Petr Baudis
0 siblings, 0 replies; 29+ messages in thread
From: Petr Baudis @ 2002-11-03 22:32 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: Jeff Garzik, Jos Hulzink, linux-kernel
Hello,
this patch (against 2.5.45) introduces sane defaults for the input layer
configuration. The most common options default to yes now, so that with simply
accepting defaults provided by make oldconfig, the 2.4 configuration can be
converted to 2.5 configuration while preserving the basic keyboard, mouse and
serial port support. This should prevent most users confusion when configuring
their first 2.5 kernel. Please apply.
drivers/input/Kconfig | 2 ++
drivers/input/keyboard/Kconfig | 2 ++
drivers/input/mouse/Kconfig | 2 ++
drivers/input/serio/Kconfig | 3 +++
4 files changed, 9 insertions(+)
Kind regards,
Petr Baudis
diff -ru linux/drivers/input/Kconfig linux+pasky/drivers/input/Kconfig
--- linux/drivers/input/Kconfig Fri Nov 1 22:21:33 2002
+++ linux+pasky/drivers/input/Kconfig Sun Nov 3 23:21:35 2002
@@ -28,6 +28,7 @@
config INPUT_MOUSEDEV
tristate "Mouse interface"
+ default y
depends on INPUT
---help---
Say Y here if you want your mouse to be accessible as char devices
@@ -45,6 +46,7 @@
config INPUT_MOUSEDEV_PSAUX
bool "Provide legacy /dev/psaux device"
+ default y
depends on INPUT_MOUSEDEV
config INPUT_MOUSEDEV_SCREEN_X
diff -ru linux/drivers/input/keyboard/Kconfig linux+pasky/drivers/input/keyboard/Kconfig
--- linux/drivers/input/keyboard/Kconfig Fri Nov 1 22:21:34 2002
+++ linux+pasky/drivers/input/keyboard/Kconfig Sun Nov 3 23:24:40 2002
@@ -3,6 +3,7 @@
#
config INPUT_KEYBOARD
bool "Keyboards"
+ default y
depends on INPUT
help
Say Y here, and a list of supported keyboards will be displayed.
@@ -12,6 +13,7 @@
config KEYBOARD_ATKBD
tristate "AT keyboard support"
+ default y
depends on INPUT && INPUT_KEYBOARD && SERIO
---help---
Say Y here if you want to use the standard AT keyboard. Usually
diff -ru linux/drivers/input/mouse/Kconfig linux+pasky/drivers/input/mouse/Kconfig
--- linux/drivers/input/mouse/Kconfig Fri Nov 1 22:21:34 2002
+++ linux+pasky/drivers/input/mouse/Kconfig Sun Nov 3 23:22:27 2002
@@ -3,6 +3,7 @@
#
config INPUT_MOUSE
bool "Mice"
+ default y
depends on INPUT
help
Say Y here, and a list of supported mice will be displayed.
@@ -12,6 +13,7 @@
config MOUSE_PS2
tristate "PS/2 mouse"
+ default y
depends on INPUT && INPUT_MOUSE && SERIO
---help---
Say Y here if you have a PS/2 mouse connected to your system. This
diff -ru linux/drivers/input/serio/Kconfig linux+pasky/drivers/input/serio/Kconfig
--- linux/drivers/input/serio/Kconfig Fri Nov 1 22:21:34 2002
+++ linux+pasky/drivers/input/serio/Kconfig Sun Nov 3 23:22:58 2002
@@ -3,6 +3,7 @@
#
config SERIO
tristate "Serial i/o support"
+ default y
---help---
Say Yes here if you have any input device that uses serial I/O to
communicate with the system. This includes the
@@ -19,6 +20,7 @@
config SERIO_I8042
tristate "i8042 PC Keyboard controller"
+ default y
depends on SERIO
---help---
i8042 is the chip over which the standard AT keyboard and PS/2
@@ -34,6 +36,7 @@
config SERIO_SERPORT
tristate "Serial port line discipline"
+ default y
depends on SERIO
---help---
Say Y here if you plan to use an input device (mouse, joystick,
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: Petition against kernel configuration options madness...
2002-11-03 20:13 ` Vojtech Pavlik
2002-11-03 22:20 ` Petr Baudis
@ 2002-11-03 22:25 ` Jos Hulzink
2002-11-04 1:40 ` Randy.Dunlap
1 sibling, 1 reply; 29+ messages in thread
From: Jos Hulzink @ 2002-11-03 22:25 UTC (permalink / raw)
To: Vojtech Pavlik, Jeff Garzik, linux-kernel
On Sunday 03 November 2002 21:13, Vojtech Pavlik wrote:
>
> All the needed options ARE enabled by default. (check arch/i386/defconfig)
Now all you need is the users to know "make defconfig". I compile kernels since 1.2.13, but I didn't know the option till today. Sure, my fault, but I'm sure I'm not the only one.
Detail: IMHO the USB keyboard and mouse support should be on, and DRI should be enabled for all video cards, but that is a minor issue...
Jos
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: Petition against kernel configuration options madness...
2002-11-03 22:25 ` Petition against kernel configuration options madness Jos Hulzink
@ 2002-11-04 1:40 ` Randy.Dunlap
0 siblings, 0 replies; 29+ messages in thread
From: Randy.Dunlap @ 2002-11-04 1:40 UTC (permalink / raw)
To: Jos Hulzink; +Cc: Vojtech Pavlik, Jeff Garzik, linux-kernel
On Sun, 3 Nov 2002, Jos Hulzink wrote:
| On Sunday 03 November 2002 21:13, Vojtech Pavlik wrote:
| >
| > All the needed options ARE enabled by default. (check arch/i386/defconfig)
|
| Now all you need is the users to know "make defconfig". I compile kernels since 1.2.13, but I didn't know the option till today. Sure, my fault, but I'm sure I'm not the only one.
|
| Detail: IMHO the USB keyboard and mouse support should be on, and DRI should be enabled for all video cards, but that is a minor issue...
so while some people are attempting to "fix" this with
defconfig or mostlikelyconfig, I'd like to remind people
of the post-halloween doc from Dave Jones. He addresses
this stuff in there. Does it possibly need even more
emphasis there? and stronger hints for people to at
least browse it before using 2.5.x for the first time?
--
~Randy
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: Petition against kernel configuration options madness...
2002-11-03 19:07 ` Vojtech Pavlik
2002-11-03 19:37 ` Petr Baudis
@ 2002-11-03 20:38 ` Arador
2002-11-03 20:40 ` Nicholas Wourms
` (3 subsequent siblings)
5 siblings, 0 replies; 29+ messages in thread
From: Arador @ 2002-11-03 20:38 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: jgarzik, josh, linux-kernel, vojtech
On Sun, 3 Nov 2002 20:07:05 +0100
Vojtech Pavlik <vojtech@suse.cz> wrote:
>
> Too bad you don't have any suggestions. I completely agree this should
> be simplified, while I wouldn't be happy to lose the possibility of not
> compiling AT keyboard support in.
What about:
<*> serial i/o (mouse, keyboard...) support"
<*> PC PS/2 and keyboard controller (i8042)
<*> PS/2 mouse support
<*> Typical (AT) keyboard support
<*> Serial port (COM) <something> support
<*> Serial port (COM) mouse support
[*] Advanced keyboard support
<*> Other keyboards here
<*> [the other Things]
Yes, it confuses people who only wants a mouse working.
Still i think it's better than selecting the driver controller
and after that selecting the device controller (if i'm understanding
the current menu ;) BTW, we'll never be able to put a <*> Mouse support
so i think that this is the best way.
Also, the current menu has some things that i dislike ;)
- Please, don't use names such "i8042 ". Most of the people
(even people in this list i guess) didn't know what
a i8042 controller is until they had to configure that ;)
"Help" is the right place for explainig that i guess ;)
- Replace "mice" by "mouse support" or something. English isn't the only
language in the earth. Many people think that the plural
of "mouse" is "mouses" ;)
- In the current menu, you can disable the i8042 thing and you still can see
the [*] Keyboard entry alone.
and another (crap) suggestion could be to put the pc speaker support under a /proc/something
and remove the menu entry ;)
^ permalink raw reply [flat|nested] 29+ messages in thread* Re: Petition against kernel configuration options madness...
2002-11-03 19:07 ` Vojtech Pavlik
2002-11-03 19:37 ` Petr Baudis
2002-11-03 20:38 ` Arador
@ 2002-11-03 20:40 ` Nicholas Wourms
2002-11-03 21:39 ` Jos Hulzink
` (2 subsequent siblings)
5 siblings, 0 replies; 29+ messages in thread
From: Nicholas Wourms @ 2002-11-03 20:40 UTC (permalink / raw)
To: linux-kernel
Vojtech Pavlik wrote:
> Too bad you don't have any suggestions. I completely agree this should
> be simplified, while I wouldn't be happy to lose the possibility of not
> compiling AT keyboard support in.
Why not set the default option for AT Keyboard support on i386 platforms to
"Y"?
Cheers,
Nicholas
^ permalink raw reply [flat|nested] 29+ messages in thread* Re: Petition against kernel configuration options madness...
2002-11-03 19:07 ` Vojtech Pavlik
` (2 preceding siblings ...)
2002-11-03 20:40 ` Nicholas Wourms
@ 2002-11-03 21:39 ` Jos Hulzink
2002-11-03 22:04 ` Nick LeRoy
2002-11-03 21:58 ` Andries Brouwer
2002-11-04 2:43 ` Miles Bader
5 siblings, 1 reply; 29+ messages in thread
From: Jos Hulzink @ 2002-11-03 21:39 UTC (permalink / raw)
To: Vojtech Pavlik, Jeff Garzik; +Cc: linux-kernel
On Sunday 03 November 2002 20:07, Vojtech Pavlik wrote:
> On Sun, Nov 03, 2002 at 12:52:48PM -0500, Jeff Garzik wrote:
> > Unfortunately I don't have any concrete suggestions for Vojtech (input
> > subsystem maintainer), just a request that it becomes easier and more
> > obvious how to configure the keyboard and mouse that is found on > 90%
> > of all Linux users computers [IMO]...
>
> Too bad you don't have any suggestions. I completely agree this should
> be simplified, while I wouldn't be happy to lose the possibility of not
> compiling AT keyboard support in.
Something I have been thinking about for a while is a quick-config option
(that sets some defaults that hold for 90% of the systems), or an expert mode
that shows extra options. Though I understand that this is hard to do, and
much hardware differs, I think it can be done for some basics like keyboard,
mouse, USB and stuff.
Yes, this will cause your kernel to be bigger than optimal, for some drivers
will be compiled in that are not used on your system. But if you want you can
optimize things away after clicking <set defaults for standard IBM PC>.
If this idea is not blown away immediately, I'm willing to work this idea out
a little, though I can understand that people call me an idiot...
Jos
^ permalink raw reply [flat|nested] 29+ messages in thread* Re: Petition against kernel configuration options madness...
2002-11-03 21:39 ` Jos Hulzink
@ 2002-11-03 22:04 ` Nick LeRoy
0 siblings, 0 replies; 29+ messages in thread
From: Nick LeRoy @ 2002-11-03 22:04 UTC (permalink / raw)
To: Jos Hulzink, Vojtech Pavlik, Jeff Garzik; +Cc: linux-kernel
On Sunday 03 November 2002 03:39 pm, Jos Hulzink wrote:
> On Sunday 03 November 2002 20:07, Vojtech Pavlik wrote:
> > On Sun, Nov 03, 2002 at 12:52:48PM -0500, Jeff Garzik wrote:
> > > Unfortunately I don't have any concrete suggestions for Vojtech (input
> > > subsystem maintainer), just a request that it becomes easier and more
> > > obvious how to configure the keyboard and mouse that is found on > 90%
> > > of all Linux users computers [IMO]...
> >
> > Too bad you don't have any suggestions. I completely agree this should
> > be simplified, while I wouldn't be happy to lose the possibility of not
> > compiling AT keyboard support in.
>
> Something I have been thinking about for a while is a quick-config option
> (that sets some defaults that hold for 90% of the systems), or an expert
> mode that shows extra options. Though I understand that this is hard to do,
> and much hardware differs, I think it can be done for some basics like
> keyboard, mouse, USB and stuff.
I like this idea!
> Yes, this will cause your kernel to be bigger than optimal, for some
> drivers will be compiled in that are not used on your system. But if you
> want you can optimize things away after clicking <set defaults for standard
> IBM PC>.
How about running the "quick config", which I can then use a base to
customize?
> If this idea is not blown away immediately, I'm willing to work this idea
> out a little, though I can understand that people call me an idiot...
Not at all!
-Nick
^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: Petition against kernel configuration options madness...
2002-11-03 19:07 ` Vojtech Pavlik
` (3 preceding siblings ...)
2002-11-03 21:39 ` Jos Hulzink
@ 2002-11-03 21:58 ` Andries Brouwer
2002-11-04 2:43 ` Miles Bader
5 siblings, 0 replies; 29+ messages in thread
From: Andries Brouwer @ 2002-11-03 21:58 UTC (permalink / raw)
To: Vojtech Pavlik; +Cc: Jeff Garzik, Jos Hulzink, linux-kernel
On Sun, Nov 03, 2002 at 08:07:05PM +0100, Vojtech Pavlik wrote:
> > Unfortunately I don't have any concrete suggestions for Vojtech (input
> > subsystem maintainer), just a request that it becomes easier and more
> > obvious how to configure the keyboard and mouse that is found on > 90%
> > of all Linux users computers [IMO]...
>
> Too bad you don't have any suggestions. I completely agree this should
> be simplified, while I wouldn't be happy to lose the possibility of not
> compiling AT keyboard support in.
Last month or so I suggested adding a hint for Appletalk, and I see
that it is there now:
config LLC
tristate "ANSI/IEEE 802.2 Data link layer protocol (IPX, Appletalk)"
Such parenthetical remarks will no doubt help a little.
You might try
--- Kconfig~ Thu Oct 31 14:15:06 2002
+++ Kconfig Sun Nov 3 22:51:45 2002
@@ -5,7 +5,7 @@
menu "Input device support"
config INPUT
- tristate
+ tristate "Input devices (needed for mouse, keyboard, ...)"
default y
---help---
Say Y here if you have any input device (mouse, keyboard, tablet,
and
--- Kconfig~ Thu Oct 31 14:15:06 2002
+++ Kconfig Sun Nov 3 22:54:28 2002
@@ -2,7 +2,7 @@
# Input core configuration
#
config SERIO
- tristate "Serial i/o support"
+ tristate "Serial i/o support (needed for keyboard and mouse)"
---help---
Say Yes here if you have any input device that uses serial I/O to
communicate with the system. This includes the
(and maybe also sth under keyboard, to tell people that what they have
is called an AT keyboard).
Andries
^ permalink raw reply [flat|nested] 29+ messages in thread* Re: Petition against kernel configuration options madness...
2002-11-03 19:07 ` Vojtech Pavlik
` (4 preceding siblings ...)
2002-11-03 21:58 ` Andries Brouwer
@ 2002-11-04 2:43 ` Miles Bader
2002-11-04 2:46 ` William Lee Irwin III
5 siblings, 1 reply; 29+ messages in thread
From: Miles Bader @ 2002-11-04 2:43 UTC (permalink / raw)
To: linux-kernel; +Cc: Vojtech Pavlik, Jeff Garzik, Jos Hulzink
Petr Baudis <pasky@ucw.cz> writes:
> > Too bad you don't have any suggestions. I completely agree this should
> > be simplified, while I wouldn't be happy to lose the possibility of not
> > compiling AT keyboard support in.
>
> Well, why can't it be enabled by default? Other options are as well, and it's
> IMHO sane to enable keyboard and mice support by default. It should clear up
> the initial confusion as well.
Keep in mind that All the World's Not a PC. No doubt those options are
enabled on the majority of kernels, by number, but linux supports many,
many types of systems, and I'll bet on fair number of them, it doesn't
make much sense to enable psaux mouse support!
So ... instead of saying `default y' for these options, how about saying
`default IM_ON_A_PC' where IM_ON_A_PC is defined somehow. How, I don't
know; it could be a separate config question in a very obvious place,
perhaps itself having `default X86'.
Perhaps this should really be two flags, one IM_ON_A_PC meaning `typical
i386 pc with legacy devices', and the other, more general, being
something like IM_ON_A_WORKSTATION. Then wierd things like psaux would
say `default IM_ON_A_PC', but more general things like keyboards would
say `default IM_ON_A_WORKSTATION'.
[Yeah, those names are sucky, I know...]
Thanks,
-Miles
--
[|nurgle|] ddt- demonic? so quake will have an evil kinda setting? one that
will make every christian in the world foamm at the mouth?
[iddt] nurg, that's the goal
^ permalink raw reply [flat|nested] 29+ messages in thread* Re: Petition against kernel configuration options madness...
2002-11-04 2:43 ` Miles Bader
@ 2002-11-04 2:46 ` William Lee Irwin III
0 siblings, 0 replies; 29+ messages in thread
From: William Lee Irwin III @ 2002-11-04 2:46 UTC (permalink / raw)
To: Miles Bader; +Cc: linux-kernel, Vojtech Pavlik, Jeff Garzik, Jos Hulzink
On Mon, Nov 04, 2002 at 11:43:18AM +0900, Miles Bader wrote:
> Keep in mind that All the World's Not a PC. No doubt those options are
> enabled on the majority of kernels, by number, but linux supports many,
> many types of systems, and I'll bet on fair number of them, it doesn't
> make much sense to enable psaux mouse support!
> So ... instead of saying `default y' for these options, how about saying
> `default IM_ON_A_PC' where IM_ON_A_PC is defined somehow. How, I don't
> know; it could be a separate config question in a very obvious place,
> perhaps itself having `default X86'.
> Perhaps this should really be two flags, one IM_ON_A_PC meaning `typical
> i386 pc with legacy devices', and the other, more general, being
> something like IM_ON_A_WORKSTATION. Then wierd things like psaux would
> say `default IM_ON_A_PC', but more general things like keyboards would
> say `default IM_ON_A_WORKSTATION'.
> [Yeah, those names are sucky, I know...]
> Thanks,
> -Miles
How about a PC subarch and turning them on by default for it?
Bill
^ permalink raw reply [flat|nested] 29+ messages in thread