Messages in this thread | ![/](/images/icornerl.gif) | | From | (Christoph Bartelmus) | Subject | Re: [PATCH] lirc for 2.5/2.6 kernels - 20030802 | Date | 09 Aug 2003 14:46:00 GMT |
| |
Hi!
Pavel Machek "pavel@suse.cz" wrote:
[...] >>> * This looks like it should be integrated with drivers/input. After >>> all remote control is just a strange keyboard. What are reasons that >>> can't be done?
Because for most drivers the decoding is done in user space by the lircd daemon.
[...] > I know about lirc project, and I'd like to see it merged, but if lirc > uses wrong interface, it is unsuitable for the kernel.
Is it the wrong interface?
> Motivation for having same code for infrared controls and normal > keyboards: normal keyboards tend to have "play"/"stop"/"vol+"/"vol-" > keys these days; certainly HP omnibook xe3 has them. It would be nice > to handle them in an uniform way.
No problem. Feed these keys to lircd. Voila: uniform interface to all applications.
There already is a patch for exactly that here: http://sourceforge.net/tracker/ index.php?func=detail&aid=670000&group_id=5444&atid=305444
I didn't have the time yet to have a closer look at this patch.
Christoph - 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/
| ![\](/images/icornerr.gif) |