Re: USB IR Receivers That Work With Lirc

[Alec L. <lea...@gm...>]

On 10/10/15 00:41, Kirk Bocek wrote:
> 
> 
> On 10/8/2015 9:22 PM, Stefan Lippers-Hollmann wrote:
>> Hi
>>
>> On 2015-10-08, Kirk Bocek wrote:
>>> On 10/8/2015 4:27 PM, Stefan Lippers-Hollmann wrote:
>>>> Looking at ir-keytable is only useful if your receiver has an RC_CORE
>>>> based driver. Regards Stefan Lippers-Hollmann
>>> How do you determine this? Is this something loaded at USB connect time?
>> It's a feature of your driver, depending on the question if your kernel
>> module has been written based on the RC_CORE subsystem or not.
>>
>> All RC_CORE based subsystem expose their features (like supported IR
>> protocols) under /sys/class/rc/, so "cat /sys/class/rc/rc0/protocols"
>> (if you have more than one device connected, the number might be larger
>> than 0). In case there is no /sys/class/rc/rc0/protocols on your
>> system, you don't have any device/ driver based on the RC_CORE
>> subsystem.
>>
>>
> 
> I restarted my host, an ESC Liva running Fedora 22, without the receiver 
> plugged in. Then I attached the receiver:
> 
> #dmesg
> ...
> [26244.389401] usb 1-2: new low-speed USB device number 3 using xhci_hcd
> [26244.563781] usb 1-2: New USB device found, idVendor=0471, idProduct=20cc
> [26244.563794] usb 1-2: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=0
> [26244.563802] usb 1-2: Product: MCE USB IR Receiver- Spinel plus
> [26244.563809] usb 1-2: Manufacturer: PHILIPS
> [26244.573527] usb 1-2: ep 0x81 - rounding interval to 64 microframes, 
> ep desc says 80 microframes
> [26244.589038] input: PHILIPS MCE USB IR Receiver- Spinel plus as 
> /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:0471:20CC.0003/input/input9
> [26244.641387] hid-generic 0003:0471:20CC.0003: input,hiddev0,hidraw2: 
> USB HID v1.00 Keyboard [PHILIPS MCE USB IR Receiver- Spinel plus] on 
> usb-0000:00:14.0-2/input0
> 
> $ls /sys/class/rc
> ls: cannot access /sys/class/rc: No such file or directory
> 
> So no RC_Core for this device? Can I use this at all with LIRC?
> 
> One of the things I tried was patching 0471:20cc into mceusb.ko and 
> force loading mceusb. This caused a hard kernel crash.

Obviously (my bad...) this kernel module is based on another framework;
the device exposed as a /sys/class/hidraw item rather than
a/sys/class/rc one.

If you are motivated enough to do some coding you could take a look at
the hiddev lirc driver (plugins/hiddev.c) which handles a number of such
beasts. Perhaps you could patch that to also support your device without
too much effort, dunno.

Cheers!

--alec