[mythtv-users] need suggestions for remote for frontend

[Jarod Wilson]

On Oct 19, 2010, at 3:35 PM, David Watkins wrote:

> On 19 October 2010 19:55, Ryan Duffy <dusteur at excite.com> wrote:
>>> You didn't get an mceusb-compatible receiver, which is what the suggestion is. You got one of the pure HID receivers. They decode in hardware
>>> and send HID events, some of which X knows what to do with natively (thus volume, numbers and a few others working). This device *is* usable
>>> with lirc using its devinput driver, or using eventlircd or inputlirc.
>> 
>> I got one of these: http://www.amazon.co.uk/Emprex-3009URF-Windows-Center-Control/dp/tech-data/B002A8HEFY/ref=de_a_smtd
>> Unfortunately there appears to be 2 types of this controller. As far as I can work out, one of them just got support added to the kernel for 2.6.35. The one I've got doesn't appear to be the same as it shows up different device names than expected.
>> 
>> However your response makes it sound as if this should make no difference and it should just work anyway.
>> 
>> Can you explain how?
> 
> If it's an HID device then you could try
> 
> # cat /proc/bus/input/devices
> 
> and see if you can see your remote showing up there.
> 
> I found mine at /dev/input/event3
> 
> 
> Then I used evtest (can't remember where I got that from) to verify
> that all keys produced an input.
> 
> 
> Then I created an lircd.conf
> 
> $ irrecord -H dev/input -d /dev/input/event3 lircd.conf


Ugh. Why do people keep doing this? Don't. :) There's ZERO difference from one devinput device to another in terms of config file. The fully fleshed out, machine-generated lircd.conf.devinput, provided by the lirc distribution itself, should be used for all devinput cases -- or at least start from there. The codes are all explicitly listed in include/linux/input.h in the linux kernel, and lircd.conf.devinput is generated automatically based on that header.


-- 
Jarod Wilson
jarod at wilsonet.com