Re: [RFC v2] Another approach to IR

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/3/09 2:47 PM, Guus Sliepen wrote:
Hello,

Some years ago I wrote a tool called "inputlirc" that translates evdev events
into LIRC events, to allow remotes that then already used the input system to
work with LIRC.  At the time, lircd itself could do this, but you had to
"train" it to "decode" evdev bitstreams. Instead, inputlirc uses a fixed
mapping between evdev names and LIRC key names, so you don't need to train or
configure anything.

No longer necessary, there's a proper devinput lircd userspace driver that when paired with an lircd.conf (auto-generated based on linux/input.h) Just Works.

http://lirc.sourceforge.net/remotes/devinput/lircd.conf.devinput

It seems that if you want to merge LIRC into the kernel, and have it generate
standard events,

It already can. If your button names in lircd.conf match button names in input.h, lircd can reinject the key presses into the input subsystem via uinput.

--
Jarod Wilson
jarod@xxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux