On Apr 27, 2011, at 2:47 PM, Heiko Baums wrote: > Am Wed, 27 Apr 2011 14:28:41 -0400 > schrieb Jarod Wilson <jarod@xxxxxxxxxxxx>: ... >> Hrm, ok, so *something* is resulting in scancodes... This is progress! >> (I think...) :) > > I'm not too optimistic. ;-) Heh, we'll get there... >>> This is one line of the ir-keytable -t output: >>> 1303909988.799949: event MSC: scancode = 4eb02 >> >> With rc-core debugging, there ought to be a line in all that dmesg >> spew that contains that scancode, which would also give us the >> protocol decoder that came up with that scancode. Based on the >> default protocol listed for your board and the length of the >> scancode, I'd guess that it is NEC Extended, but it could also be >> RC-5X or maybe Sony... > > This is what dmesg says: I meant dmesg output after pressing the button that results in the ir-keytable 4eb02 output... If I had to guess though, that was from the "1" key on your remote, and the issue here we're facing is that the keymap only has the last part of the scancode for lookup... However, I think I do at least see why you have no active protocols. It looks like the v4l-utils ir-keytable rule is loading a new map (probably the terratec_cinergy_xs one), which doesn't have a specific protocol listed, so no protocols get enabled. Mauro, what's the expected behavior of ir-keytable when it loads a keymap that says "type: UNKNOWN"? Heiko, here's something to try: Make a backup copy of /etc/rc_keymaps/terratec_cinergy_xs, and then alter the original, so that it says "type: NEC" and prefix each of the scancodes with 4eb (i.e., 0x41 KEY_HOME -> 0x4eb41 KEY_HOME). Then load that, and see if things start actually working... (I'm sort of shooting in the dark here, but I think its worth a try). -- Jarod Wilson jarod@xxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
