[mythtv-users] MCE remote after 0.21 -> 0.27 upgrade
Alec Leamas
leamas.alec at gmail.com
Mon Sep 7 17:55:27 UTC 2015
On 07/09/15 19:00, Jerome Yuzyk wrote:
> [250159.289045] usb 5-1: new full-speed USB device number 3 using uhci_hcd
> [250159.448065] usb 5-1: New USB device found, idVendor=0609, idProduct=031d
> [250159.448073] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [250159.448078] usb 5-1: Product: eHome Infrared Transceiver
> [250159.448083] usb 5-1: Manufacturer: SMK
> [250159.448088] usb 5-1: SerialNumber: SM007OxF
> [250159.456072] Registered IR keymap rc-rc6-mce
> [250159.456239] input: Media Center Ed. eHome Infrared Remote Transceiver (0609:031d) as /devices/pci0000:00/0000:00:1a.2/usb5/5-1/5-1:1.0/rc/rc0/input16
> [250159.456298] rc0: Media Center Ed. eHome Infrared Remote Transceiver (0609:031d) as /devices/pci0000:00/0000:00:1a.2/usb5/5-1/5-1:1.0/rc/rc0
> [250159.456399] input: MCE IR Keyboard/Mouse (mceusb) as /devices/virtual/input/input17
> [250159.457540] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
> [250159.600066] mceusb 5-1:1.0: Registered SMK eHome Infrared Transceiver with mce emulator interface version 1
> [250159.600074] mceusb 5-1:1.0: 2 tx ports (0x0 cabled) and 2 rx sensors (0x1 active)
OK, basically this looks good. Now, following [1], there is two ways,
both of which should work from what we know now:
- Use the kernel decoding. This means configuring the lirc-keytable
device maps so it works, and then let lirc work on top of this using the
devinput driver on a /dev/input/event* device.
- Or let LIRC do the decoding itself, reading the raw timing data
from the kernel using a correct, perhaps custom-specific lircd.conf.
This means using the default driver, probably on the /dev/lirc0 device
Have you any idea what route you would prefer?
Cheers!'
--alec
[1] http://lirc.sourceforge.net/lirc.org/html/configuration-guide.html
More information about the mythtv-users
mailing list