On Wed, Feb 22, 2006 at 04:09:33PM -0500, Dmitry Torokhov wrote:
> > How about simply this patch instead?
> >
> > Setting autorepeat will not be possible on 'dumb' keyboards anymore by
> > default, but since these usually are special forms of hardware anyway,
> > like the DRAC3, this shouldn't be an issue for most users. Using
> > 'softrepeat' on these keyboards will restore the behavior for users that
> > need it.
>
> I am not keen on changing the default behaviour... How many dumb
> keyboards are out there?
Apart from the DRAC3, some home-made Sun-to-PS2 converter, and a single
non-x86 embedded box, I don't recall anything. Answer: very few.
There may be users, though, that use this option to force the detection
of the keyboard when not really plugged in, eg. for flaky KVMs. I've
Googled for that usage, but found none.
> I'd rather turn atkbd.softrepeat into a 3-state switch...
We could, but the more I think about it, the stronger I'm convinced that
the dumbkbd => softrepeat => softraw option implication chain is wrong.
The second implication is necessary, but with dumbkbd it's quite likely
you won't want softraw.
--
Vojtech Pavlik
Director SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
