I'am using the remote plugin with the keymap "alles.rc5", found on vdr-portal.de. Now I'm going to use another remote but I need to create an new keymap, because the keys are not defined. I found somewhere on the net, that u must load the modul dvb-ttpci with the parameter av7110_irdebug=1 or something (don't really know at the moment) - but this doesnt work any longer. I'am using a 2.6 kernel with the dvb cvs-kernel from april 15th.
dev0 root # modinfo dvb-ttpci parmtype: debug:int parm: debug:debug level (bitmask, default 0)
that's the only debug thing i can select, but there are no entries for the keymap in syslog.
I need the keycodes in syslog while pressing the buttons on the remote to create the keymap. How?
thx and cu /devzero
devzero wrote:
I'am using the remote plugin with the keymap "alles.rc5", found on vdr-portal.de. Now I'm going to use another remote but I need to create an new keymap, because the keys are not defined. I found somewhere on the net, that u must load the modul dvb-ttpci with the parameter av7110_irdebug=1 or something (don't really know at the moment) - but this doesnt work any longer. I'am using a 2.6 kernel with the dvb cvs-kernel from april 15th.
dev0 root # modinfo dvb-ttpci parmtype: debug:int parm: debug:debug level (bitmask, default 0)
that's the only debug thing i can select, but there are no entries for the keymap in syslog.
Use debug=16 for ir debugging. For kernel 2.6, the module parameter has been changed recently.
I need the keycodes in syslog while pressing the buttons on the remote to create the keymap. How?
Do you really need a custom keymap? The remote plugin can load a keymap which will work for most remote controls.
Oliver
dev0 root # modinfo dvb-ttpci parmtype: debug:int parm: debug:debug level (bitmask, default 0)
that's the only debug thing i can select, but there are no entries for the keymap in syslog.
Use debug=16 for ir debugging. For kernel 2.6, the module parameter has been changed recently.
That's not working. Nothing in Syslog. I'm using metalog, but I think that doesn't matter.
devzero wrote:
dev0 root # modinfo dvb-ttpci parmtype: debug:int parm: debug:debug level (bitmask, default 0)
that's the only debug thing i can select, but there are no entries for the keymap in syslog.
Use debug=16 for ir debugging. For kernel 2.6, the module parameter has been changed recently.
That's not working. Nothing in Syslog. I'm using metalog, but I think that doesn't matter.
Before you can play with evtest/debug output you have to load a keymap first. Any RC5 keymap will do.
Oliver
Oliver Endriss schrieb:
That's not working. Nothing in Syslog. I'm using metalog, but I think that doesn't matter.
Before you can play with evtest/debug output you have to load a keymap first. Any RC5 keymap will do.
Oliver
Thank u, maybe I can't read. :) I didn't know about the loading of a keymap, I'll give it a try.
devzero schrieb:
Oliver Endriss schrieb:
That's not working. Nothing in Syslog. I'm using metalog, but I think that doesn't matter.
Before you can play with evtest/debug output you have to load a keymap first. Any RC5 keymap will do.
Oliver
Thank u, maybe I can't read. :) I didn't know about the loading of a keymap, I'll give it a try.
Hmmm are u sure? Only the keys in keymap are listed in syslog.
devzero wrote:
devzero schrieb:
Oliver Endriss schrieb:
Before you can play with evtest/debug output you have to load a keymap first. Any RC5 keymap will do.
Thank u, maybe I can't read. :) I didn't know about the loading of a keymap, I'll give it a try.
Hmmm are u sure? Only the keys in keymap are listed in syslog.
Yes. I am sure, for example...
known key: | Apr 28 15:16:33 orion kernel: dvb-ttpci: av7110_emit_key(): #########00000000######### addr 0 data 0x00 (keycode 11) | Apr 28 15:16:36 orion kernel: dvb-ttpci: av7110_emit_key(): #########00000800######### addr 0 data 0x00 (keycode 11)
unknown key: | Apr 28 15:16:39 orion kernel: dvb-ttpci: av7110_emit_key(): #########0000001e######### addr 0 data 0x1e (keycode 0) | Apr 28 15:16:39 orion kernel: av7110_emit_key: unknown key 0x1e!!
If there is no output the remote control does not transmit a RC5 code. Extended RC5 codes do not work. This is a firmware limitation.
Oliver
-
devzero -
Oliver Endriss