Re: MCE receiver problem
Petric Frank <[email protected]>
| Newsgroups | gmane.comp.hardware.lirc |
|---|---|
| Message-ID | <4007930.UctQTsQ4yp@main> |
Hello Alec, On Friday, March 17, 2017 Alec Leamas wrote: > On 15/03/17 01:29, Petric Frank wrote: > > maybe this is not exactly a lirc problem. Please point me to correct > > location if i am wrong here. > > As presented, this is a kernel issue - the basic decoding and > ir-keytable is part of the kernel package. This was my impression also. I think the main problem here ist that the ir remote is not detected as remote control device and no entry /sys/class/rc/rc* is created. So i was not able to switch to the correct keymap and i'm stuck with the default one. > Getting help on these usually > best done on the distribution help channels (gentoo in your case, but it > might make sense to try one of the bigger distros if you don't get any > answer) Will do. But the starting point is to find out wether the (non working) keys are seen at the USB receiver before going further. This to exclude a hardware problem. Is there an easy way to "sniff" the ir receiver ? And perhaps evaluate the correct (kernel) scan codes as result ... > It might be that adding new keys to the remote is complicated using the > kernel stuff - to be honest, I'm not quite sure. In this case, one > option is to use the LIRC decoding instead of the kernel tools. If this > is what you want, you might want to look into [1]. To be able to use > keys not supported by the kernel you need to use the 'default' driver. Currently lirc 0.9.0 is marked stable in gentoo. Would it be better to use the latest unstable version in gentoo of lirc (0.9.4) ? At a first read of [1] - take the data via devinput driver by lirc from /dev/input/eventxx, correct ? As i have read older versions of lirc had a driver named mceusb(2). This module seem no more part of lirc. Would this be a problem ? kind regards Petric [1] http://lirc.org/html/configuration-guide.html ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot