100 ms _does not help anybody_ because when a glitch occurs, it is not
single shot, but repetitive, and fast - therefore you will end up with
duplicates.
>
> Note that scancode repeat is not good enough: many keys produce an e0 xx pair
> and repeat that; more complicated things also occur.
Of course this is covered, please have a look at the patch.
> So, you could consider intercepting repetition at the keycode
> instead of the scancode level.
At the keycode level I cannot make the difference between key down and
key up. I rely on both keydowns and ups in my patch. I tried with
various approaches, including keycodes - this is the best.
>
> [I also find that aesthetically more satisfying: the scancode level
> really shows the raw keyboard with all its quirks.]
Access to keycode is only provided (elegantly) in keyboard.c, which is
common to all architectures.
Andrei
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/