[mythtv-users] USB IR Receivers

[Kirk Bocek]

On 9/2/2015 12:27 PM, Kirk Bocek wrote:
>
>
> On 9/2/2015 12:06 PM, Alec Leamas wrote:
>> On 02/09/15 19:16, Kirk Bocek wrote:
>>>
>>>
>>> On 9/2/2015 10:00 AM, Kirk Bocek wrote:
>>>>
>>>>
>>>>
>>>> First Liva with the old Microsoft receiver: 4.0.8-200.fc21.x86_64
>>>>
>>>> Second Liva with the Chinese knockoff receiver recommended here:
>>>> 4.1.5-100.fc21.x86_64
>>>>
>>>> Info on the knockoff receiver, udevadm info -a
>>>> /sys/bus/usb/devices/1-2:1.0:
>>>
>>> Alec's last suggestions for me were regarding the fact that my receiver
>>> is automatically loading as a keyboard through the usb-hid 
>>> interface. Is
>>> anyone familiar with this:
>>>
>>> http://www.math.ucla.edu/~jimc/documents/bugfix/17-ir-keyboard.html
>>>
>>> I'm not at home right now, so I can't test this. This posting goes back
>>> to 2010 and I wonder how applicable it is. Part of my problem is that I
>>> am getting *no* output out of ir-keytable at all.
>>
>> Combined with the fact that mceusb isn't loaded properly I find 
>> Jerry's and Roger's argument quite compelling.  That your old remote 
>> works doesn't really change that, there is certainly a chance that 
>> the exact combination of computer, remote and kernel exhibits this 
>> bug. The only way to know is to recompile the kernel, though.
>>
>> Personally, I don't think your link is a plausible solution. That is 
>> not to say I've tried it, or even read it carefully. it certainly 
>> won't help is the sub driver is the problem.
>>
>> *If* the mceusb drivar was loaded correctly the kernel should have 
>> setup a /sys/class/rc entry (unless you have some strange udev or 
>> modprobe stuff).
>>
>> Perhaps you should double-check that your hardware is supported:
>> http://lxr.free-electrons.com/source/drivers/media/rc/mceusb.c (use 
>> the right version!)
>>
>> Another avenue would be to recompile the mceusb module with debug 
>> enabled to see if it comes anything sane from that. Re-compiling a 
>> module is a simple, light-weight task.
>>
>> On a sidenote, we have established the fact that this problem is not 
>> an LIRC one, it's in the kernel.
>>
>
> No, the receiver is listed by name "Philips Infrared Transceiver - 
> Spinel plus", but not by ID:
>
> $ lsusb
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 002: ID 0471:20cc Philips (or NXP)
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> ID 20CC is not there at all. So what I'd really like to do is edit the 
> source for the current module and just compile that rather than the 
> whole kernel. Easy to get the source for the kernel I'm currently 
> using. I can find and edit this file easy enough.
>
> Can anyone help me with the command line for compiling an individual 
> driver file?
>

Well, as usual this is looking harder than I think it needs to be. 
Installing the kernel-devel package and the kernel-modules package does 
*not* include the mceusb.c source file. <sigh>