Re: HVR900H : IR Remote Control
Le 17/11/2010 20:33, Massis Sirapian a écrit :
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=
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 majord...@vger.kernel.org
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/pci:00/:00:1d.0/usb2/2-1/2-1.4/rc/rc0/input7
[ 227.643965] rc0: tm5600/60x0 IR (tm6000 #0) as
/devices/pci:00/: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 majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
Does it mean that the IR isn't wired in the case of HVR900H ? When you
said that your Terratec equals the HVR900H, does it imply that if IR
works on cinergy xe, it should on the HVR900H?
Thank you
Massis
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: HVR900H : IR Remote Control
On Thu, Nov 18, 2010 at 2:59 PM, Massis Sirapian msirap...@free.fr wrote: Does it mean that the IR isn't wired in the case of HVR900H ? When you said that your Terratec equals the HVR900H, does it imply that if IR works on cinergy xe, it should on the HVR900H? One thing you may wish to consider is that if I recall the Terratec remotes are typically NEC and the Hauppauge remotes are typically RC5. So it's possible that only the NEC support is working in the current tm6010 driver, which is why the Hauppauge remote doesn't work. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: HVR900H : IR Remote Control
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=
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 majord...@vger.kernel.org
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/pci:00/:00:1d.0/usb2/2-1/2-1.4/rc/rc0/input7
[ 227.643965] rc0: tm5600/60x0 IR (tm6000 #0) as
/devices/pci:00/: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 majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: HVR900H : IR Remote Control
Le 16/11/2010 21:32, Stefan Ringel a écrit : Am 16.11.2010 21:26, schrieb Massis Sirapian: Le 15/11/2010 22:08, Stefan Ringel a écrit : Am 15.11.2010 22:00, schrieb Massis Sirapian: Le 15/11/2010 18:43, Stefan Ringel a écrit : Am 15.11.2010 10:15, schrieb Richard Zidlicky: On Sun, Nov 14, 2010 at 08:22:44PM +0100, Massis Sirapian wrote: Thanks Stefan. I've checked the /drivers/media/IR/keymaps of the kernel source directory, but nothing seems to fit my remote, which is a DSR-0012 : http://lirc.sourceforge.net/remotes/hauppauge/DSR-0112.jpg. FYI, this remote is identical to that shipped with (most?) Haupauge Ministicks and the codes reportedly match the rc-dib0700-rc5.c keymap. However I have not figured out how to make the userspace work with the new ir-code yet. Richard With my terratec cinergy hybrid xe (equal yours hvr900h) I have this: localhost:/usr/src/src/tm6000_alsa/utils/v4l-utils # ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event5) with: Driver tm6000, table rc-nec-terratec-cinergy-xs Supported protocols: NEC RC-5 Enabled protocols: NEC I can change outside the keytable. Just loading tm6000-dvb, I have this : [ 253.829422] IR NEC protocol handler initialized [ 253.846608] IR RC5(x) protocol handler initialized [ 253.883882] tm6000: module is from the staging directory, the quality is unknown, you have been warned. [ 253.886611] tm6000 v4l2 driver version 0.0.2 loaded [ 253.887558] tm6000: alt 0, interface 0, class 255 [ 253.887574] tm6000: alt 0, interface 0, class 255 [ 253.887575] tm6000: Bulk IN endpoint: 0x82 (max size=512 bytes) [ 253.887577] tm6000: alt 0, interface 0, class 255 [ 253.887578] tm6000: alt 1, interface 0, class 255 [ 253.887579] tm6000: ISOC IN endpoint: 0x81 (max size=3072 bytes) [ 253.887580] tm6000: alt 1, interface 0, class 255 [ 253.887581] tm6000: alt 1, interface 0, class 255 [ 253.887582] tm6000: INT IN endpoint: 0x83 (max size=4 bytes) [ 253.887583] tm6000: alt 2, interface 0, class 255 [ 253.887584] tm6000: alt 2, interface 0, class 255 [ 253.887586] tm6000: alt 2, interface 0, class 255 [ 253.887587] tm6000: alt 3, interface 0, class 255 [ 253.887588] tm6000: alt 3, interface 0, class 255 [ 253.887589] tm6000: alt 3, interface 0, class 255 [ 253.887590] tm6000: New video device @ 480 Mbps (2040:6600, ifnum 0) [ 253.887591] tm6000: Found Hauppauge WinTV HVR-900H / WinTV USB2-Stick [ 253.48] IR RC6 protocol handler initialized [ 253.890209] IR JVC protocol handler initialized [ 253.891515] IR Sony protocol handler initialized [ 253.893815] lirc_dev: IR Remote Control driver registered, major 250 [ 253.894722] IR LIRC bridge handler initialized [ 254.806122] Board version = 0x67980bf4 [ 255.197098] board=0x67980bf4 [ 255.320786] tm6000 #0: i2c eeprom 00: 01 59 54 45 12 01 00 02 00 00 00 40 40 20 00 66 .YTE...@@ .f [ 255.512277] tm6000 #0: i2c eeprom 10: 69 00 10 20 40 01 02 03 48 00 79 00 62 00 72 00 i.. @...H.y.b.r. [ 255.703783] tm6000 #0: i2c eeprom 20: ff 00 64 ff ff ff ff ff ff ff ff ff ff ff ff ff ..d. [ 255.895281] tm6000 #0: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 256.086786] tm6000 #0: i2c eeprom 40: 10 03 48 00 56 00 52 00 39 00 30 00 30 00 48 00 ..H.V.R.9.0.0.H. [ 256.278289] tm6000 #0: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 256.469783] tm6000 #0: i2c eeprom 60: 30 ff ff ff 0f ff ff ff ff ff 0a 03 32 00 2e 00 0...2... [ 256.661287] tm6000 #0: i2c eeprom 70: 3f 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ?... [ 256.852786] tm6000 #0: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 257.044307] tm6000 #0: i2c eeprom 90: 30 ff ff ff 16 03 34 00 30 00 33 00 32 00 32 00 0.4.0.3.2.2. [ 257.235798] tm6000 #0: i2c eeprom a0: 33 00 36 00 39 00 30 00 35 00 00 00 77 00 ff ff 3.6.9.0.5...w... [ 257.427295] tm6000 #0: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 257.618794] tm6000 #0: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 257.810303] tm6000 #0: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 258.001810] tm6000 #0: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 258.193291] tm6000 #0: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 258.372825] [ 258.378849] tuner 4-0061: chip found @ 0xc2 (tm6000 #0) [ 258.400777] xc2028 4-0061: creating new instance [ 258.400779] xc2028 4-0061: type set to XCeive xc2028/xc3028 tuner [ 258.400781] Setting firmware parameters for xc2028 [ 258.427221] xc2028 4-0061: Loading 81 firmware images from xc3028L-v36.fw, type: xc2028 firmware, ver 3.6 [ 258.668063] xc2028 4-0061: Loading firmware for type=BASE (1), id . [ 333.245767] xc2028 4-0061: Loading firmware for type=(0), id b700. [ 334.510473] SCODE (2000), id b700:
Re: HVR900H : IR Remote Control
Am 16.11.2010 21:42, schrieb Massis Sirapian: Le 16/11/2010 21:32, Stefan Ringel a écrit : Am 16.11.2010 21:26, schrieb Massis Sirapian: Le 15/11/2010 22:08, Stefan Ringel a écrit : Am 15.11.2010 22:00, schrieb Massis Sirapian: Le 15/11/2010 18:43, Stefan Ringel a écrit : Am 15.11.2010 10:15, schrieb Richard Zidlicky: On Sun, Nov 14, 2010 at 08:22:44PM +0100, Massis Sirapian wrote: Thanks Stefan. I've checked the /drivers/media/IR/keymaps of the kernel source directory, but nothing seems to fit my remote, which is a DSR-0012 : http://lirc.sourceforge.net/remotes/hauppauge/DSR-0112.jpg. FYI, this remote is identical to that shipped with (most?) Haupauge Ministicks and the codes reportedly match the rc-dib0700-rc5.c keymap. However I have not figured out how to make the userspace work with the new ir-code yet. Richard With my terratec cinergy hybrid xe (equal yours hvr900h) I have this: localhost:/usr/src/src/tm6000_alsa/utils/v4l-utils # ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event5) with: Driver tm6000, table rc-nec-terratec-cinergy-xs Supported protocols: NEC RC-5 Enabled protocols: NEC I can change outside the keytable. Just loading tm6000-dvb, I have this : [ 253.829422] IR NEC protocol handler initialized [ 253.846608] IR RC5(x) protocol handler initialized [ 253.883882] tm6000: module is from the staging directory, the quality is unknown, you have been warned. [ 253.886611] tm6000 v4l2 driver version 0.0.2 loaded [ 253.887558] tm6000: alt 0, interface 0, class 255 [ 253.887574] tm6000: alt 0, interface 0, class 255 [ 253.887575] tm6000: Bulk IN endpoint: 0x82 (max size=512 bytes) [ 253.887577] tm6000: alt 0, interface 0, class 255 [ 253.887578] tm6000: alt 1, interface 0, class 255 [ 253.887579] tm6000: ISOC IN endpoint: 0x81 (max size=3072 bytes) [ 253.887580] tm6000: alt 1, interface 0, class 255 [ 253.887581] tm6000: alt 1, interface 0, class 255 [ 253.887582] tm6000: INT IN endpoint: 0x83 (max size=4 bytes) [ 253.887583] tm6000: alt 2, interface 0, class 255 [ 253.887584] tm6000: alt 2, interface 0, class 255 [ 253.887586] tm6000: alt 2, interface 0, class 255 [ 253.887587] tm6000: alt 3, interface 0, class 255 [ 253.887588] tm6000: alt 3, interface 0, class 255 [ 253.887589] tm6000: alt 3, interface 0, class 255 [ 253.887590] tm6000: New video device @ 480 Mbps (2040:6600, ifnum 0) [ 253.887591] tm6000: Found Hauppauge WinTV HVR-900H / WinTV USB2-Stick [ 253.48] IR RC6 protocol handler initialized [ 253.890209] IR JVC protocol handler initialized [ 253.891515] IR Sony protocol handler initialized [ 253.893815] lirc_dev: IR Remote Control driver registered, major 250 [ 253.894722] IR LIRC bridge handler initialized [ 254.806122] Board version = 0x67980bf4 [ 255.197098] board=0x67980bf4 [ 255.320786] tm6000 #0: i2c eeprom 00: 01 59 54 45 12 01 00 02 00 00 00 40 40 20 00 66 .YTE...@@ .f [ 255.512277] tm6000 #0: i2c eeprom 10: 69 00 10 20 40 01 02 03 48 00 79 00 62 00 72 00 i.. @...H.y.b.r. [ 255.703783] tm6000 #0: i2c eeprom 20: ff 00 64 ff ff ff ff ff ff ff ff ff ff ff ff ff ..d. [ 255.895281] tm6000 #0: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 256.086786] tm6000 #0: i2c eeprom 40: 10 03 48 00 56 00 52 00 39 00 30 00 30 00 48 00 ..H.V.R.9.0.0.H. [ 256.278289] tm6000 #0: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 256.469783] tm6000 #0: i2c eeprom 60: 30 ff ff ff 0f ff ff ff ff ff 0a 03 32 00 2e 00 0...2... [ 256.661287] tm6000 #0: i2c eeprom 70: 3f 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ?... [ 256.852786] tm6000 #0: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 257.044307] tm6000 #0: i2c eeprom 90: 30 ff ff ff 16 03 34 00 30 00 33 00 32 00 32 00 0.4.0.3.2.2. [ 257.235798] tm6000 #0: i2c eeprom a0: 33 00 36 00 39 00 30 00 35 00 00 00 77 00 ff ff 3.6.9.0.5...w... [ 257.427295] tm6000 #0: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 257.618794] tm6000 #0: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 257.810303] tm6000 #0: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 258.001810] tm6000 #0: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 258.193291] tm6000 #0: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 258.372825] [ 258.378849] tuner 4-0061: chip found @ 0xc2 (tm6000 #0) [ 258.400777] xc2028 4-0061: creating new instance [ 258.400779] xc2028 4-0061: type set to XCeive xc2028/xc3028 tuner [ 258.400781] Setting firmware parameters for xc2028 [ 258.427221] xc2028 4-0061: Loading 81 firmware images from xc3028L-v36.fw, type: xc2028 firmware, ver 3.6 [ 258.668063] xc2028 4-0061: Loading firmware for type=BASE (1), id . [ 333.245767] xc2028 4-0061: Loading firmware for type=(0), id
Re: HVR900H : IR Remote Control
On Sun, Nov 14, 2010 at 08:22:44PM +0100, Massis Sirapian wrote: Thanks Stefan. I've checked the /drivers/media/IR/keymaps of the kernel source directory, but nothing seems to fit my remote, which is a DSR-0012 : http://lirc.sourceforge.net/remotes/hauppauge/DSR-0112.jpg. FYI, this remote is identical to that shipped with (most?) Haupauge Ministicks and the codes reportedly match the rc-dib0700-rc5.c keymap. However I have not figured out how to make the userspace work with the new ir-code yet. Richard -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: HVR900H : IR Remote Control
Am 15.11.2010 10:15, schrieb Richard Zidlicky: On Sun, Nov 14, 2010 at 08:22:44PM +0100, Massis Sirapian wrote: Thanks Stefan. I've checked the /drivers/media/IR/keymaps of the kernel source directory, but nothing seems to fit my remote, which is a DSR-0012 : http://lirc.sourceforge.net/remotes/hauppauge/DSR-0112.jpg. FYI, this remote is identical to that shipped with (most?) Haupauge Ministicks and the codes reportedly match the rc-dib0700-rc5.c keymap. However I have not figured out how to make the userspace work with the new ir-code yet. Richard With my terratec cinergy hybrid xe (equal yours hvr900h) I have this: localhost:/usr/src/src/tm6000_alsa/utils/v4l-utils # ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event5) with: Driver tm6000, table rc-nec-terratec-cinergy-xs Supported protocols: NEC RC-5 Enabled protocols: NEC I can change outside the keytable. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: HVR900H : IR Remote Control
Le 15/11/2010 18:43, Stefan Ringel a écrit : Am 15.11.2010 10:15, schrieb Richard Zidlicky: On Sun, Nov 14, 2010 at 08:22:44PM +0100, Massis Sirapian wrote: Thanks Stefan. I've checked the /drivers/media/IR/keymaps of the kernel source directory, but nothing seems to fit my remote, which is a DSR-0012 : http://lirc.sourceforge.net/remotes/hauppauge/DSR-0112.jpg. FYI, this remote is identical to that shipped with (most?) Haupauge Ministicks and the codes reportedly match the rc-dib0700-rc5.c keymap. However I have not figured out how to make the userspace work with the new ir-code yet. Richard With my terratec cinergy hybrid xe (equal yours hvr900h) I have this: localhost:/usr/src/src/tm6000_alsa/utils/v4l-utils # ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event5) with: Driver tm6000, table rc-nec-terratec-cinergy-xs Supported protocols: NEC RC-5 Enabled protocols: NEC I can change outside the keytable. Just loading tm6000-dvb, I have this : [ 253.829422] IR NEC protocol handler initialized [ 253.846608] IR RC5(x) protocol handler initialized [ 253.883882] tm6000: module is from the staging directory, the quality is unknown, you have been warned. [ 253.886611] tm6000 v4l2 driver version 0.0.2 loaded [ 253.887558] tm6000: alt 0, interface 0, class 255 [ 253.887574] tm6000: alt 0, interface 0, class 255 [ 253.887575] tm6000: Bulk IN endpoint: 0x82 (max size=512 bytes) [ 253.887577] tm6000: alt 0, interface 0, class 255 [ 253.887578] tm6000: alt 1, interface 0, class 255 [ 253.887579] tm6000: ISOC IN endpoint: 0x81 (max size=3072 bytes) [ 253.887580] tm6000: alt 1, interface 0, class 255 [ 253.887581] tm6000: alt 1, interface 0, class 255 [ 253.887582] tm6000: INT IN endpoint: 0x83 (max size=4 bytes) [ 253.887583] tm6000: alt 2, interface 0, class 255 [ 253.887584] tm6000: alt 2, interface 0, class 255 [ 253.887586] tm6000: alt 2, interface 0, class 255 [ 253.887587] tm6000: alt 3, interface 0, class 255 [ 253.887588] tm6000: alt 3, interface 0, class 255 [ 253.887589] tm6000: alt 3, interface 0, class 255 [ 253.887590] tm6000: New video device @ 480 Mbps (2040:6600, ifnum 0) [ 253.887591] tm6000: Found Hauppauge WinTV HVR-900H / WinTV USB2-Stick [ 253.48] IR RC6 protocol handler initialized [ 253.890209] IR JVC protocol handler initialized [ 253.891515] IR Sony protocol handler initialized [ 253.893815] lirc_dev: IR Remote Control driver registered, major 250 [ 253.894722] IR LIRC bridge handler initialized [ 254.806122] Board version = 0x67980bf4 [ 255.197098] board=0x67980bf4 [ 255.320786] tm6000 #0: i2c eeprom 00: 01 59 54 45 12 01 00 02 00 00 00 40 40 20 00 66 .YTE...@@ .f [ 255.512277] tm6000 #0: i2c eeprom 10: 69 00 10 20 40 01 02 03 48 00 79 00 62 00 72 00 i.. @...H.y.b.r. [ 255.703783] tm6000 #0: i2c eeprom 20: ff 00 64 ff ff ff ff ff ff ff ff ff ff ff ff ff ..d. [ 255.895281] tm6000 #0: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 256.086786] tm6000 #0: i2c eeprom 40: 10 03 48 00 56 00 52 00 39 00 30 00 30 00 48 00 ..H.V.R.9.0.0.H. [ 256.278289] tm6000 #0: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 256.469783] tm6000 #0: i2c eeprom 60: 30 ff ff ff 0f ff ff ff ff ff 0a 03 32 00 2e 00 0...2... [ 256.661287] tm6000 #0: i2c eeprom 70: 3f 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ?... [ 256.852786] tm6000 #0: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 257.044307] tm6000 #0: i2c eeprom 90: 30 ff ff ff 16 03 34 00 30 00 33 00 32 00 32 00 0.4.0.3.2.2. [ 257.235798] tm6000 #0: i2c eeprom a0: 33 00 36 00 39 00 30 00 35 00 00 00 77 00 ff ff 3.6.9.0.5...w... [ 257.427295] tm6000 #0: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 257.618794] tm6000 #0: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 257.810303] tm6000 #0: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 258.001810] tm6000 #0: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 258.193291] tm6000 #0: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 258.372825] [ 258.378849] tuner 4-0061: chip found @ 0xc2 (tm6000 #0) [ 258.400777] xc2028 4-0061: creating new instance [ 258.400779] xc2028 4-0061: type set to XCeive xc2028/xc3028 tuner [ 258.400781] Setting firmware parameters for xc2028 [ 258.427221] xc2028 4-0061: Loading 81 firmware images from xc3028L-v36.fw, type: xc2028 firmware, ver 3.6 [ 258.668063] xc2028 4-0061: Loading firmware for type=BASE (1), id . [ 333.245767] xc2028 4-0061: Loading firmware for type=(0), id b700. [ 334.510473] SCODE (2000), id b700: [ 334.510476] xc2028 4-0061: Loading SCODE for type=MONO SCODE HAS_IF_4320 (60008000), id
Re: HVR900H : IR Remote Control
Am 15.11.2010 22:00, schrieb Massis Sirapian: Le 15/11/2010 18:43, Stefan Ringel a écrit : Am 15.11.2010 10:15, schrieb Richard Zidlicky: On Sun, Nov 14, 2010 at 08:22:44PM +0100, Massis Sirapian wrote: Thanks Stefan. I've checked the /drivers/media/IR/keymaps of the kernel source directory, but nothing seems to fit my remote, which is a DSR-0012 : http://lirc.sourceforge.net/remotes/hauppauge/DSR-0112.jpg. FYI, this remote is identical to that shipped with (most?) Haupauge Ministicks and the codes reportedly match the rc-dib0700-rc5.c keymap. However I have not figured out how to make the userspace work with the new ir-code yet. Richard With my terratec cinergy hybrid xe (equal yours hvr900h) I have this: localhost:/usr/src/src/tm6000_alsa/utils/v4l-utils # ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event5) with: Driver tm6000, table rc-nec-terratec-cinergy-xs Supported protocols: NEC RC-5 Enabled protocols: NEC I can change outside the keytable. Just loading tm6000-dvb, I have this : [ 253.829422] IR NEC protocol handler initialized [ 253.846608] IR RC5(x) protocol handler initialized [ 253.883882] tm6000: module is from the staging directory, the quality is unknown, you have been warned. [ 253.886611] tm6000 v4l2 driver version 0.0.2 loaded [ 253.887558] tm6000: alt 0, interface 0, class 255 [ 253.887574] tm6000: alt 0, interface 0, class 255 [ 253.887575] tm6000: Bulk IN endpoint: 0x82 (max size=512 bytes) [ 253.887577] tm6000: alt 0, interface 0, class 255 [ 253.887578] tm6000: alt 1, interface 0, class 255 [ 253.887579] tm6000: ISOC IN endpoint: 0x81 (max size=3072 bytes) [ 253.887580] tm6000: alt 1, interface 0, class 255 [ 253.887581] tm6000: alt 1, interface 0, class 255 [ 253.887582] tm6000: INT IN endpoint: 0x83 (max size=4 bytes) [ 253.887583] tm6000: alt 2, interface 0, class 255 [ 253.887584] tm6000: alt 2, interface 0, class 255 [ 253.887586] tm6000: alt 2, interface 0, class 255 [ 253.887587] tm6000: alt 3, interface 0, class 255 [ 253.887588] tm6000: alt 3, interface 0, class 255 [ 253.887589] tm6000: alt 3, interface 0, class 255 [ 253.887590] tm6000: New video device @ 480 Mbps (2040:6600, ifnum 0) [ 253.887591] tm6000: Found Hauppauge WinTV HVR-900H / WinTV USB2-Stick [ 253.48] IR RC6 protocol handler initialized [ 253.890209] IR JVC protocol handler initialized [ 253.891515] IR Sony protocol handler initialized [ 253.893815] lirc_dev: IR Remote Control driver registered, major 250 [ 253.894722] IR LIRC bridge handler initialized [ 254.806122] Board version = 0x67980bf4 [ 255.197098] board=0x67980bf4 [ 255.320786] tm6000 #0: i2c eeprom 00: 01 59 54 45 12 01 00 02 00 00 00 40 40 20 00 66 .YTE...@@ .f [ 255.512277] tm6000 #0: i2c eeprom 10: 69 00 10 20 40 01 02 03 48 00 79 00 62 00 72 00 i.. @...H.y.b.r. [ 255.703783] tm6000 #0: i2c eeprom 20: ff 00 64 ff ff ff ff ff ff ff ff ff ff ff ff ff ..d. [ 255.895281] tm6000 #0: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 256.086786] tm6000 #0: i2c eeprom 40: 10 03 48 00 56 00 52 00 39 00 30 00 30 00 48 00 ..H.V.R.9.0.0.H. [ 256.278289] tm6000 #0: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 256.469783] tm6000 #0: i2c eeprom 60: 30 ff ff ff 0f ff ff ff ff ff 0a 03 32 00 2e 00 0...2... [ 256.661287] tm6000 #0: i2c eeprom 70: 3f 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ?... [ 256.852786] tm6000 #0: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 257.044307] tm6000 #0: i2c eeprom 90: 30 ff ff ff 16 03 34 00 30 00 33 00 32 00 32 00 0.4.0.3.2.2. [ 257.235798] tm6000 #0: i2c eeprom a0: 33 00 36 00 39 00 30 00 35 00 00 00 77 00 ff ff 3.6.9.0.5...w... [ 257.427295] tm6000 #0: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 257.618794] tm6000 #0: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 257.810303] tm6000 #0: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 258.001810] tm6000 #0: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 258.193291] tm6000 #0: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 258.372825] [ 258.378849] tuner 4-0061: chip found @ 0xc2 (tm6000 #0) [ 258.400777] xc2028 4-0061: creating new instance [ 258.400779] xc2028 4-0061: type set to XCeive xc2028/xc3028 tuner [ 258.400781] Setting firmware parameters for xc2028 [ 258.427221] xc2028 4-0061: Loading 81 firmware images from xc3028L-v36.fw, type: xc2028 firmware, ver 3.6 [ 258.668063] xc2028 4-0061: Loading firmware for type=BASE (1), id . [ 333.245767] xc2028 4-0061: Loading firmware for type=(0), id b700. [ 334.510473] SCODE (2000), id b700: [ 334.510476] xc2028 4-0061: Loading SCODE
Re: HVR900H : IR Remote Control
Am 14.11.2010 15:37, schrieb Massis Sirapian: Hi, I have discovered, upgrading my old WinTV PCI Hauppauge card to a HVR-900H USB stick how much the IR userspace has evolved. I'm using the 2.6.36 kernel provided by Debian in its experimental repository. Loading the tm6000_dvb works fine (even if it takes a while when I modprobe it while the USB stick is already plugged). Kaffeine sees and uses correctly the device. However, I'd like to use the IR remote control. It seems to be recognized, as dmesg | grep -i lirc gives : [ 123.306153] lirc_dev: IR Remote Control driver registered, major 250 [ 123.306932] IR LIRC bridge handler initialized I have no event nor input device created. I've understood from Jarod's pages that the new IR userspace doesn't necessarily require lirc, but sees the IR receiver as a keyboard. No such device is present in /proc/bus/input/devices inputlirc + irw don't show anything. Am I missing something here ? Do I have to load a specific module ? I have found a lot of information concerning imon, but none I can apply to my HVR-900H/tm6000 case. Thanks in advance Massis -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html HVR900H doesn't use lirc. It generates an input device, if a rc_map is present for this device. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: HVR900H : IR Remote Control
Le 14/11/2010 16:47, Stefan Ringel a écrit : Am 14.11.2010 15:37, schrieb Massis Sirapian: Hi, I have discovered, upgrading my old WinTV PCI Hauppauge card to a HVR-900H USB stick how much the IR userspace has evolved. I'm using the 2.6.36 kernel provided by Debian in its experimental repository. Loading the tm6000_dvb works fine (even if it takes a while when I modprobe it while the USB stick is already plugged). Kaffeine sees and uses correctly the device. However, I'd like to use the IR remote control. It seems to be recognized, as dmesg | grep -i lirc gives : [ 123.306153] lirc_dev: IR Remote Control driver registered, major 250 [ 123.306932] IR LIRC bridge handler initialized I have no event nor input device created. I've understood from Jarod's pages that the new IR userspace doesn't necessarily require lirc, but sees the IR receiver as a keyboard. No such device is present in /proc/bus/input/devices inputlirc + irw don't show anything. Am I missing something here ? Do I have to load a specific module ? I have found a lot of information concerning imon, but none I can apply to my HVR-900H/tm6000 case. Thanks in advance Massis -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html HVR900H doesn't use lirc. It generates an input device, if a rc_map is present for this device. Thanks Stefan. I've checked the /drivers/media/IR/keymaps of the kernel source directory, but nothing seems to fit my remote, which is a DSR-0012 : http://lirc.sourceforge.net/remotes/hauppauge/DSR-0112.jpg. Were you talking about these rc_map modules? If so and if there is corresponding module for my remote, how can I contribute as I have one? -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: HVR900H : IR Remote Control
Hello Massis, On 11/14/2010 08:22 PM, Massis Sirapian wrote: Thanks Stefan. I've checked the /drivers/media/IR/keymaps of the kernel source directory, but nothing seems to fit my remote, which is a DSR-0012 : http://lirc.sourceforge.net/remotes/hauppauge/DSR-0112.jpg. Were you talking about these rc_map modules? If so and if there is corresponding module for my remote, how can I contribute as I have one? First of all you need to check for the codes if they appear when you pressing buttons. If you have /dev/input/eventX number then you can use: input-events X where X is the event number related with you IR receiver then you can make a map for you remote (based on that codes you've got) you can also create the temporary map for testing and load it using command: input-kbd -f your_map_file X where X - event number, your_map_file - a file with key mappings in format: key_code = KEY_something, ie: 146 = KEY_0 regards -- Mariusz Bialonczyk jabber/e-mail: ma...@skyboo.net http://manio.skyboo.net -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: HVR900H : IR Remote Control
Le 14/11/2010 21:49, Mariusz Bialonczyk a écrit : Hello Massis, On 11/14/2010 08:22 PM, Massis Sirapian wrote: Thanks Stefan. I've checked the /drivers/media/IR/keymaps of the kernel source directory, but nothing seems to fit my remote, which is a DSR-0012 : http://lirc.sourceforge.net/remotes/hauppauge/DSR-0112.jpg. Were you talking about these rc_map modules? If so and if there is corresponding module for my remote, how can I contribute as I have one? First of all you need to check for the codes if they appear when you pressing buttons. If you have /dev/input/eventX number then you can use: input-events X where X is the event number related with you IR receiver then you can make a map for you remote (based on that codes you've got) you can also create the temporary map for testing and load it using command: input-kbd -f your_map_file X where X - event number, your_map_file - a file with key mappings in format: key_code = KEY_something, ie: 146 = KEY_0 regards Hi Mariusz, I'd be delighted to do that, but no event device is created. That's the reason of my first message : except tm6000-dvb, should I load another module? It feels like something is preventing the event device from being created. cat /proc/bus/input/devices gives : I: Bus=0003 Vendor=046d Product=c018 Version=0111 N: Name=Logitech USB Optical Mouse P: Phys=usb-:00:1a.0-1.3/input0 S: Sysfs=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input0 U: Uniq= H: Handlers=mouse0 event0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0003 Vendor=0461 Product=0010 Version=0110 N: Name=NOVATEK USB Keyboard P: Phys=usb-:00:1a.0-1.4/input0 S: Sysfs=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input1 U: Uniq= H: Handlers=sysrq kbd event1 B: EV=120013 B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=0461 Product=0010 Version=0110 N: Name=NOVATEK USB Keyboard P: Phys=usb-:00:1a.0-1.4/input1 S: Sysfs=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/input/input2 U: Uniq= H: Handlers=kbd event2 B: EV=13 B: KEY=200 39fad941d001 1e 0 B: MSC=10 I: Bus=0010 Vendor=001f Product=0001 Version=0100 N: Name=PC Speaker P: Phys=isa0061/input0 S: Sysfs=/devices/platform/pcspkr/input/input3 U: Uniq= H: Handlers=kbd event3 B: EV=40001 B: SND=6 I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4 U: Uniq= H: Handlers=kbd event4 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: EV=3 B: KEY=10 0 I: Bus=0003 Vendor=046d Product=08ad Version=0100 N: Name=zc3xx P: Phys=usb-:00:1a.0-1.5/input0 S: Sysfs=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/input/input6 U: Uniq= H: Handlers=kbd event6 B: EV=3 B: KEY=10 0 0 0 Good night Massis -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: HVR900H : IR Remote Control
On Nov 14, 2010, at 2:22 PM, Massis Sirapian wrote: Le 14/11/2010 16:47, Stefan Ringel a écrit : Am 14.11.2010 15:37, schrieb Massis Sirapian: Hi, I have discovered, upgrading my old WinTV PCI Hauppauge card to a HVR-900H USB stick how much the IR userspace has evolved. I'm using the 2.6.36 kernel provided by Debian in its experimental repository. Loading the tm6000_dvb works fine (even if it takes a while when I modprobe it while the USB stick is already plugged). Kaffeine sees and uses correctly the device. However, I'd like to use the IR remote control. It seems to be recognized, as dmesg | grep -i lirc gives : [ 123.306153] lirc_dev: IR Remote Control driver registered, major 250 [ 123.306932] IR LIRC bridge handler initialized I have no event nor input device created. I've understood from Jarod's pages that the new IR userspace doesn't necessarily require lirc, but sees the IR receiver as a keyboard. No such device is present in /proc/bus/input/devices inputlirc + irw don't show anything. Am I missing something here ? Do I have to load a specific module ? I have found a lot of information concerning imon, but none I can apply to my HVR-900H/tm6000 case. Thanks in advance Massis -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html HVR900H doesn't use lirc. It generates an input device, if a rc_map is present for this device. Thanks Stefan. I've checked the /drivers/media/IR/keymaps of the kernel source directory, but nothing seems to fit my remote, which is a DSR-0012 : http://lirc.sourceforge.net/remotes/hauppauge/DSR-0112.jpg. Were you talking about these rc_map modules? If so and if there is corresponding module for my remote, how can I contribute as I have one? Your device doesn't appear to have IR wired up. The driver that drives it is likely requesting the IR modules be loaded, but your particular board's support isn't implemented -- thus no input or lirc devices that have shown up. -- Jarod Wilson ja...@wilsonet.com -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
