Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure
From: Krzysztof Halasa <khc@pm.waw.pl>
Date: 2009-11-23 20:51:30
Also in:
linux-media, lkml
Possibly related (same subject, not in this thread)
- 2009-12-13 · Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure · <hidden>
- 2009-12-09 · Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure · Mauro Carvalho Chehab <hidden>
- 2009-12-09 · Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure · Mauro Carvalho Chehab <hidden>
- 2009-12-09 · Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure · Mauro Carvalho Chehab <hidden>
- 2009-12-08 · 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 <khc@pm.waw.pl>
Dmitry Torokhov [off-list ref] writes:
Curreently the "scan" codes in the input layer serve just to help users to map whatever the device emits into a proper input event code so that the rest of userspace would not have to care and would work with all types of devices (USB, PS/2, etc). I would not want to get to the point where the raw codes are used as a primary data source.
The "key" interface is not flexible enough at present.
Again, I would prefer to keep EV_KEY/KEY_* as the primary event type for keys and buttons on all devices.
Primary, I think so. -- Krzysztof Halasa