From: Jarod W. <ja...@wi...> - 2010-11-11 04:03:50
|
On Nov 9, 2010, at 1:38 AM, Andreas Westin wrote: > On 2010-11-09 02:49, Jarod Wilson wrote: >> On Nov 8, 2010, at 1:37 PM, Andreas Westin wrote: >> >>> On 2010-11-08 18:48, Jarod Wilson wrote: >>>> On Nov 8, 2010, at 12:17 PM, Andreas Westin wrote: >>>> ... >>>>> Nothing that looks like an error though, except I get these when I press a key: >>>>> [227300.551353] ir_keydown: iMON Remote (15c2:0036): key down event, key 0x0069, scancode 0x2000050 >>>>> [227300.655055] ir_g_keycode_from_table: iMON Remote (15c2:0036): scancode 0x2000050 keycode 0x69 >>>>> [227300.655060] ir_g_keycode_from_table: iMON Remote (15c2:0036): scancode 0x2000050 keycode 0x69 >>>>> [227300.750794] ir_keyup: keyup key 0x0069 >>>>> >>>>> I don't see those when I press "play" for instance but evtest register it as (Misc) and evtest lists this: >>>>> Event code 207 (Play) >>>> >>>> Wait, what? If evtest shows an event code 207 (Play) coming through, then the driver is behaving as expected. Does the devinput lircd.conf you're using have KEY_PLAY in it? >>>> >>> >>> Sorry wasn't clear, I meant that when I start evtest it lists a bunch of event codes when it starts. There is no event code 207 coming through. >> >> Ah, okay. Damn. I continue to be baffled here then. What output do you get from 'ir-keytable -r'? Perhaps the KEY_PLAY mapping isn't actually being replaced. Output from 'ir-keytable -v' would also be interesting. >> > > sudo ir-keytable -r: > Enabled protocols: RC-6 Ugh. Something is awry with ir-keytable. The -r is supposed to dump the device's entire keymap. Its not working here either. I'll have to investigate that some. Ugh. -- Jarod Wilson ja...@wi... |