Messages in this thread | | | Date | Wed, 20 Aug 2003 23:58:12 +0100 | From | Jamie Lokier <> | Subject | Re: Input issues - key down with no key up |
| |
Andries Brouwer wrote: > > For my purposes, I need to use an "ioctl" to set a keycode for each > > scancode, so adding an ioctl to set the no-keyup status is no hassle > > for me. However the suggest approach of auto-detecting keys which > > have no up event would probably a good idea. > > I would be unhappy. > We need a solid keyboard driver that actually works. > Not some fragile construction that has tricks built-in > so as to make things work for every kernel developer.
Synthesising an UP event after receiving a DOWN from the keyboard, and nothing else for that key for > (repeat delay + a bit more) time looks like a good plan to me, UNLESS there are keys which do report UP when the key is released (as opposed to immediately after the DOWN), and also don't repeat.
Unrelated: I have some messages from my laptop, Toshiba Satellite 4070CDT:
atkbd.c: Unknown key (set 2, scancode 0x94, in isa0060/serio0) pressed. atkbd.c: Unknown key (set 2, scancode 0xbf, in isa0060/serio0) pressed. atkbd.c: Unknown key (set 2, scancode 0xa1, in isa0060/serio0) pressed.
Enjoy, -- Jamie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |