On Mon, 7 Mar 2005, Oliver Endriss wrote: > In kernel 2.6 there are 2 ioctls to manipulate keymaps > - EVIOCGKEYCODE > - EVIOCSKEYCODE > Fine, they could be used to implement generic keymaps. But... I think this is what Gerd is using in his http://dl.bytesex.org/cvs-snapshots/input-<version>.tar.gz keymap-upload-tool. (He just pointed that out in another mail) > Most applications do some key mapping on their own. > Why don't we simply fill all holes in the keymaps of the drivers with > some unique codes? This would avoid dead keys which are the main problem > right know. The holes are huge, because e.g. dibusb-devices (and as far as I can see the cinergyt2 as well) are able to deliver the code of all NEC-protocol-compatible remote controls (is this the RC5?), not just the ones which are boxed. The NOVA-T USB2 additionally supports a different kind of RC-protocol, which seems to be more spreaded, because all remotes I own can be used with the receiver inside the NOVA-T. I'm not a remote control expert, so I can't say which protocol it is or whatever. Hardcoding this every table inside the driver is simply not possible. Of course both types have different data structures, to display the key and if it was a key repeat and so. regards, Patrick. -- Mail: patrick.boettcher@xxxxxxx WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/
