From: Johan V. <jvr...@sq...> - 2014-05-15 21:50:17
|
Alec Leamas <lea...@gm...> writes: > The default driver is definitely part of lirc-0.9.1-pre3. Have you > tried to just use --with-driver=userspace which builds all userspace > drivers? Thanks, that did help. Now I've got a lircd with debug that shows the same problems as the original lircd. I run it with: # daemons/lircd -D1 --device=/dev/lirc0 -u --output /var/run/lirc/lircd -n -L ./xx.log ~pi/lircd.conf I get the following messages in the log file: May 15 23:06:31 raspbmc lircd: lircd(default) ready, using /var/run/lirc/lircd May 15 23:06:37 raspbmc lircd: trying "LG_6711R1P089A" remote May 15 23:06:37 raspbmc lircd: sync May 15 23:06:37 raspbmc lircd: header May 15 23:06:37 raspbmc lircd: pre: b4b4 May 15 23:06:37 raspbmc lircd: code: 1ae5 May 15 23:06:37 raspbmc lircd: pre May 15 23:06:37 raspbmc lircd: found: ENTER May 15 23:06:37 raspbmc lircd: 4bc2e0 0 0 0 0 0 0 0 0 1 May 15 23:06:37 raspbmc lircd: release_gap: 208681 May 15 23:06:37 raspbmc lircd: trying "LG_6711R1P089A" remote May 15 23:06:37 raspbmc lircd: sync May 15 23:06:37 raspbmc lircd: repeat header May 15 23:06:37 raspbmc lircd: pre May 15 23:06:37 raspbmc lircd: found: ENTER May 15 23:06:37 raspbmc lircd: 4bc2e0 4bc2e0 4bc2e0 1 1 0 0 1 1 1 May 15 23:06:37 raspbmc lircd: release_gap: 208681 Everything indicates that the remote is working, the signals are detected (in the above case, I pressed ENTER on the remote). Keys can be read by irw from /var/run/lirc/lircd -- but still nothing appears on /dev/input/event2. Using additional debug prints I found the cause: for events to be written to the uinput device the name of the event must match one of the names in the input_map.inc. My config contained event names that lacked the KEY_ prefix so they were not understood, and skipped. Since I copied an existing config I must have had the back luck of picking one that was not good. Thanks for the assistance, I'll proceed from here... -- Johan |