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:14:07
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>
Mauro Carvalho Chehab [off-list ref] writes:
True, but this means that everyone with an IR will need to use lirc.
I think that if the input layer (instead of raw code) is used, a utility which only sets the mapping(s) would suffice. I.e. no daemon.
/me thinks that, whatever decided with those lirc drivers, this should be applied also to the existing V4L/DVB drivers.
Certainly.
IMO, it would be better to load the tables at the boot time (or at the corresponding hotplug event, for USB devices).
Sure (unless the "raw code" interface is in use). Though maybe the raw code interface should be done in a simple library instead of requiring the daemon. -- Krzysztof Halasa