load the tm6000 module with the parameter "ir_debug=1". (not the
tm6000_dvb), and check dmsg after you pressed a button. Have the
received code the same from the map?
I have only
[ 5232.133592] tm5600/60x0 IR (tm6000 #0)/ir: ir->get_key result
data=0000
endlessly, and nothing seems to change when I press a button.
can you test a little change in tm6000-input.c. The dprintk line "this
line" move to "here", and then testing it.
return;
}
dprintk("ir->get_key result data=%04x\n", poll_result.rc_data); // this
line
if (ir->key) {
// here
ir_keydown(ir->rc, poll_result.rc_data, 0);
ir->key = 0;
--
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
I've just tested the new kernel compiled with the modifie tm6000-cards.c
Nothing happens when I press a button :
[ 227.643920] input: tm5600/60x0 IR (tm6000 #0) as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/rc/rc0/input7
[ 227.643965] rc0: tm5600/60x0 IR (tm6000 #0) as
/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/rc/rc0
[ 227.759492] usbcore: registered new interface driver tm6000
[ 229.015963] tm6000: open called (dev=video1)
are the last lines of dmesg, and my pressing any button doesn't change
anything.
Massis
--
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
