[mythtv-users] USB IR Receivers

[Alec Leamas]

On 31/08/15 02:36, Kirk Bocek wrote:
>
>
> On 8/30/2015 4:59 PM, Nick Morrott wrote:
>> On 28 August 2015 at 22:32, Kirk Bocek <t004 at kbocek.com> wrote:
>>
>>> I received my receiver and got it plugged into my new ECS Liva running
>>> Fedora 21. It seems to get recogized:
>>>
>>> [178998.885410] usb 1-1: new low-speed USB device number 3 using
>>> xhci_hcd
>>> [178999.061504] usb 1-1: New USB device found, idVendor=0471,
>>> idProduct=20cc
>>> [178999.061517] usb 1-1: New USB device strings: Mfr=1, Product=2,
>>> SerialNumber=0
>>> [178999.061526] usb 1-1: Product: MCE USB IR Receiver- Spinel plus
>>> [178999.061533] usb 1-1: Manufacturer: PHILIPS
>>> [178999.064751] usb 1-1: ep 0x81 - rounding interval to 64
>>> microframes, ep
>>> desc says 80 microframes
>>> [178999.085843] input: PHILIPS MCE USB IR Receiver- Spinel plus as
>>> /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:0471:20CC.0003/input/input9
>>>
>> Just wondering if this is the problem:
>>
>>> [178999.137558] 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-1/input0
>> It's getting detected as a USB keyboard, not as an IR receiver?
>>
>> What does the following show?
>>
>> $ ls -l /sys/class/rc/
>>
>> Do you see an rc node for the receiver?
>>
>
> No, no such directory.
>
> However:
>
> $ir-keytable
> --device=/dev/input/by-path/pci-0000:00:14.0-usb-0:1:1.0-event-ir -r
>
> scancode 0x700e1 = KEY_LEFTSHIFT (0x2a)
> scancode 0x700e2 = KEY_LEFTALT (0x38)
> scancode 0x700e3 = KEY_LEFTMETA (0x7d)
> scancode 0x700e4 = KEY_RIGHTCTRL (0x61)
> scancode 0x700e5 = KEY_RIGHTSHIFT (0x36)
> scancode 0x700e6 = KEY_RIGHTALT (0x64)
> scancode 0x700e7 = KEY_RIGHTMETA (0x7e)
> scancode 0x70000 = KEY_RESERVED (0x00)
> scancode 0x70001 = KEY_RESERVED (0x00)
> scancode 0x70002 = KEY_RESERVED (0x00)
> scancode 0x70003 = KEY_RESERVED (0x00)
> scancode 0x70004 = KEY_A (0x1e)
> scancode 0x70005 = KEY_B (0x30)
> scancode 0x70006 = KEY_C (0x2e)
>   ...
>
> So we do have something here. I see note about installing the output of
> -r elsewhere so it can be used.

This basically means that you should be able to use the devinput driver 
and configuration file using this device as input (or, perhaps better, 
the corresponding link under /dev/input/by_id). This is with the 
devinput limitations, notably the lack of sending (blasting) support.

Also, depending on what buttons you actually are pressing, the key 
mappings looks strange... If a plain 'left' button is decoded as 
LEFTSHIFT, LEFTALT and/or LEFTMETA ther moight be a problem. It should 
then be resolved at the kernel side (ir-keytable has many options, none 
of which I'm used to).



Cheers!

--alec