[mythtv-users] Trying To Get Two IR Receivers Working

[Kirk Bocek]

On 10/15/2015 1:20 PM, Alec Leamas wrote:
> Well, your must first decide if you want to use the kernel decoding (i.
> e., the devinput driver) or lirc's own - the default driver.
>
> Thoughts?
>
>

I had previously thought that you needed to have lircd running to be 
able run irexec. But someone said that is now a loadable module and will 
run in either mode. So I guess it doesn't matter. Some further info. 
This device also attaches as event9:

$ls -la /dev/input/by-id/
total 0
drwxr-xr-x. 2 root root 100 Oct 15 13:19 .
drwxr-xr-x. 4 root root 340 Oct 15 13:19 ..
lrwxrwxrwx. 1 root root   9 Oct 15 13:15 
usb-Chicony_USB_Keyboard-event-if01 -> ../event5
lrwxrwxrwx. 1 root root   9 Oct 15 13:15 
usb-Chicony_USB_Keyboard-event-kbd -> ../event3
lrwxrwxrwx. 1 root root   9 Oct 15 13:19 
usb-Topseed_Technology_Corp._eHome_Infrared_Transceiver_TS00098N-event-if00 
-> ../event9

so stopping lircd and confirming with ir-keytable:

$ir-keytable -t -d /dev/input/event9
Testing events. Please, press CTRL-C to abort.
1444940704.665261: event type EV_MSC(0x04): scancode = 0x800f0
1444940704.665261: event type EV_SYN(0x00).
1444940713.017303: event type EV_MSC(0x04): scancode = 0x800f0
1444940713.017303: event type EV_SYN(0x00).

Although this *was* working without the -d parameter. Also, not every 
keypress is caught. Only every few. 'cat /dev/input/event9' gives noise 
in a similar infrequent way.