[linux-dvb] Re: NEWSTRUCT and Remote Control

[Holger Waechtler <holger@convergence.de>]

Oliver Endriss wrote:
> On Wednesday 04 September 2002 09:28, Holger Waechtler wrote:
> 
>>Oliver Endriss wrote:
>>
>>>is the internal remote control port of the Hauppauge DVB-S Nexus
>>>2.1 supported by the NEWSTRUCT driver (CVS 2002-09-02)?
>>
>>yes, it is. You have to load an appropriate keymap and inversion
>>config setting using the av7110_loadkeys utility in DVB/apps/. There
>>is also a README which describes how to build your own keymaps for
>>new remote controls.
>>
>>When you have more than one card in your box, the IR input of the
>>first card will be used.
>>
>>When you get no interrupts (== no kernel messages in debug mode) you
>>probably have a wrong protocol (RC5 vs. RCMM) or inversion setting or
>>there is a problem with the electrical connection.
>>
>>Please let me know when problems arise,
> 
> 
> Thank you for your quick response.
> 
> I have a very simple setup: just one card: Hauppauge DVB-S Nexus Rev 2.1
> I'm using the vanilla Hauppauge remote control (should be RC5 protocol).
> 
> The card and the remote control work perfectly with the old driver (CVS 
> 05aug2002). So there is no electrical problem.
> 
> Right now I checked out the NEWSTRUCT driver (CVS 04sep2002) again.
> I loaded dvb-ttpci.o with 'av7110_debug=1' and ' av7110_ir_debug=1',
> but there is just no debug message (not even a GPIO interrupt) when I 
> press any key on the remote control.
> 
> apps/av7110_loadkeys/README states (I read this before posting the 
> question):
> | In order to write a new keymap you might want to see the raw key
> | values in the kernel log. Use
> |
> |   # insmod dvb-ttpci.o av7110_ir_debug=1
> |
> | in order to enable some verbosity in the av7110_ir driver. Then watch
> | the kernel log while pressing your remote control keys.
> 
> But there are *no* raw key values in the kernel log. At least I should 
> see some debug messages, no matter whether the keymap is correct or 
> not. Just to be safe I tested all supplied keymaps with inversion on 
> and off. Same result: nothing.
> 
> Finally I replaced Root and Dpram with the ones of the old driver:  
> Now I get GPIO interrupts and evtest reports some keys.
> | Sep  4 11:59:32 orion kernel: GPIO0 irq 8 4
> | Sep  4 11:59:32 orion kernel: GPIO0 irq 08
> | Sep  4 11:59:32 orion kernel: av7110: ircommand = 80000001
> | Sep  4 11:59:32 orion kernel: GPIO0 irq exit 0
> | Sep  4 11:59:32 orion kernel: #########80000001######### key 01
> | pressed (keycode 2)
> | Sep  4 11:59:33 orion kernel: GPIO0 irq 8 4
> | Sep  4 11:59:33 orion kernel: GPIO0 irq 08
> | Sep  4 11:59:33 orion kernel: av7110: ircommand = 00000001
> | Sep  4 11:59:33 orion kernel: GPIO0 irq exit 0
> 
> Looks like a firmware problem, doesn't it?

hmm, I just tested again with the new firmware, it works fine for me. 
Anyway, I found a type in the README concerning the usage of 
av7110_loadkeys. For the Hauppauge remote control you should use:

$ ./av7110_loadkeys [-i] hauppauge.rc5 > /proc/av7110_ir

I'll update the README in CVS.

Holger



-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe linux-dvb" as subject.