2.6.9-22.EL(CentOS 4.2) is what I currently use.
2.4.20 was where I first saw, in keyboard.c, the
workaround that throws away a second break code.
I think I like the new design for the user input
system: separate the protocol layer from the raw port.
But, would it be nice for the atkbd driver to still
provide a raw (or passthrough) mode?
Thanks,
Congjun Yang
--- Dmitry Torokhov <[email protected]> wrote:
> On Saturday 01 July 2006 05:55, Jan-Benedict Glaw
> wrote:
> > * All protocol drivers (eg. the atkbd driver)
> will *never* ever
> > stuff the raw I/O anywhere.
>
> Actually some of them do via EV_MSC/MSC_RAW events.
> So raw code should be
> available through evdev nodes and also on x86
> keyboard driver in raw mode
> should also pass raw data through (from atkbd only).
>
> Congjun, what 2.6.x kernel have you tried?
>
> --
> Dmitry
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
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]
