![]() | |||||||||||||
Messages in this thread |
> Well, I think it's a bad idea to have the userspace tool know about the > e0 thing at all. It should be just opaque numbers to it. But how is the user to invent these opaque numbers? She uses showkey -s to see what scancodes a key produces, and then setkeycodes to assign a keycode to them. > I don't have a problem with swapping the set3 table, if setkeycodes > works reasonably now for scancodes above 128. Above 128, yes. Above 256, no. The interface is a char - 8 bits only. (So, right now, NR_KEYS > 256 is not useful.) Andries - 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:00 [from the cache] ©2003-2008 | |||||||||||||