From: <cv...@kr...> - 2011-03-28 10:28:45
|
On Fri, 25 Mar 2011 15:39:21 -0400, Jarod Wilson wrote: >> when I press the KEY_UP now for the first time, irw shows nothing, >> and the syslog says: >> >> Mar 25 14:49:52 htpc kernel: [ 293.524776] intf0 decoded packet: 01 >> 00 00 f2 00 00 00 00 >> Mar 25 14:49:52 htpc kernel: [ 293.524787] imon 1-1.6.1:1.0: >> imon_incoming_packet: unknown keypress, code 0x10000f2 >> >> Pressing KEY_UP the second time, irw shows >> >> 0000000080010067 00 KEY_UP devinput >> >> and the syslog shows >> >> Mar 25 14:50:00 htpc kernel: [ 302.016015] intf0 decoded packet: 01 >> 00 00 f2 00 00 00 00 >> Mar 25 14:50:00 htpc kernel: [ 302.016025] imon 1-1.6.1:1.0: >> imon_incoming_packet: unknown keypress, code 0x10000f2 >> Mar 25 14:50:00 htpc kernel: [ 302.056102] intf0 decoded packet: 01 >> 00 00 f2 00 00 00 00 >> Mar 25 14:50:00 htpc kernel: [ 302.056112] imon 1-1.6.1:1.0: >> imon_incoming_packet: unknown keypress, code 0x10000f2 > > This happens, because of the way the pad-to-keys filtering in the > imon > driver works. The pad sends hundreds of distinct signals, which we > try > to gather up and determine an up/down/left/right direction from. If > we > don't have enough data to work with (see the pad threshold bits in > the > code), then we don't find a direction, and the raw value from the pad > leaks through (when in keyboard mode -- in mouse mode, its just mouse > movement). Basically, its nothing to worry about. You may want to > tweak > your pad_thresh value (via modparam) to fine-tune how much pressure > is > needed on the pad to register up/down/left/right though. I'm getting these errors/messages in syslog as well when I use a harmony configured as imon-pad. And the harmony has normal buttons, not this pad. So it seems that, for a better responsiveness, I should add 0x10000f2 and the other codes somehow to lirc. I tried editing the imon-pad keytable and then loading it into the kernel with ir-keytable. But that didn't help, pressing keys still caused the "unknown keypress" messages in syslog. How would I need to edit the keytable (or anything else) in order to get the additional 0x10000f2 code recognized? I can then add the other codes as well, and am happy to feed back the result to you, if that helps (others). >> Mar 25 14:50:00 htpc lircd-0.8.7-pre3[959]: you are using an >> obsolete devinput config file: Success >> Mar 25 14:50:00 htpc lircd-0.8.7-pre3[959]: get the new version at >> http://lirc.sourceforge.net/remotes/devinput/lircd.conf.devinput: >> Success > Yeah, I think you actually want the one in lirc git, I need to push > out a bunch of remote definition updates, including that one. The new one was not included in the 0.9.0 archive, right? I tried the devinput from that archive, but it was similar to the one I already have installed. |