![]() | |||||||||||
Messages in this thread |
* James H. Cloos Jr. <cloos@jhcloos.com>: > The one example I quoted above, atkbd_set2_keycode[0xb2] is in fact 0. > > Perhaps your kb is doing something unusual w/ the key release events. I would think so! The patch that fixed the issue with the key release events was this - I submitted it to Alan who then put it into ac and then it went into 2.4.x... Details: http://www.informatik.uni-freiburg.de/~leibl/lol/ Patch excerpt: + /* The following 'if' is a workaround for hardware + * which sometimes send the key release event twice */ + unsigned char next_scancode = scancode|up_flag; + if (up_flag && next_scancode==prev_scancode) { + /* unexpected 2nd release event */ + } else { + prev_scancode=next_scancode; + put_queue(next_scancode); + } I haven't checked if 2.6.0 already has this! -- Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de Charite Campus Mitte Tel. +49 (0)30-450 570-155 Referat V a - Kommunikationsnetze - Fax. +49 (0)30-450 570-916 AIM: ralfpostfix - 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/ | ||||||||||
| Last update: 2005-03-22 13:46 [from the cache] ©2003-2008 | |||||||||||