Messages in this thread | | | Date | Mon, 23 Nov 2009 17:19:23 +0100 | From | Stefan Richter <> | Subject | Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure |
| |
Krzysztof Halasa wrote: > Mauro Carvalho Chehab <mchehab@redhat.com> writes: > >> Event input has the advantage that the keystrokes will provide an unique >> representation that is independent of the device. > > This can hardly work as the only means, the remotes have different keys, > the user almost always has to provide customized key<>function mapping.
Modern input drivers in the mainline kernel have a scancode-to-keycode translation table (or equivalent) which can be overwritten by userspace. The mechanism to do that is the EVIOCSKEYCODE ioctl.
(This is no recommendation for lirc. I have no idea whether a pulse/space -> scancode -> keycode translation would be practical there.) -- Stefan Richter -=====-==--= =-== =-=== http://arcgraph.de/sr/
| |