On Feb 20, 2008 10:34 PM, Filippo Argiolas <filippo.argiolas@xxxxxxxxx> wrote:
2008/2/20, Matthew Vermeulen <mattvermeulen@xxxxxxxxx>:
> Ok - just thought I'd try the patch on the latest tree and see what
> happens... as expected, it put an end to the syslog flooding - but nothing
> really has improved... I still see a single error line in the syslog every
> time I press a key - so obviously the kernel is seeing something happen, but
> deciding it's unknown and not taking it any further. Something must be wrong
> with some mappings somewhere.. :S Here's the syslog output anyway - there is
> one line for every key press:
>
> Feb 20 22:07:07 matthew-desktop kernel: [38161.388548] dib0700: Unknown
> remote controller key: 12 7E 1 0
> Feb 20 22:07:09 matthew-desktop kernel: [38162.678839] dib0700: Unknown
> remote controller key: 18 7C 1 0
> Feb 20 22:07:10 matthew-desktop kernel: [38162.906413] dib0700: Unknown
> remote controller key: 18 7C 1 0
> Feb 20 22:07:14 matthew-desktop kernel: [38165.183338] dib0700: Unknown
> remote controller key: 1C 4D 1 0
> Feb 20 22:07:18 matthew-desktop kernel: [38167.156040] dib0700: Unknown
> remote controller key: 1F 7D 1 0
> Feb 20 22:07:21 matthew-desktop kernel: [38168.598632] dib0700: Unknown
> remote controller key: 19 43 1 0
>
> This is very annoying because it seems that polling the syslog every 150ms
> might even give you something if you could work it out ;) Anyway.. any ideas
> where to now...?
Ok, I didn't take a look at your previous messages, so I was thinking> happens... as expected, it put an end to the syslog flooding - but nothing
> really has improved... I still see a single error line in the syslog every
> time I press a key - so obviously the kernel is seeing something happen, but
> deciding it's unknown and not taking it any further. Something must be wrong
> with some mappings somewhere.. :S Here's the syslog output anyway - there is
> one line for every key press:
>
> Feb 20 22:07:07 matthew-desktop kernel: [38161.388548] dib0700: Unknown
> remote controller key: 12 7E 1 0
> Feb 20 22:07:09 matthew-desktop kernel: [38162.678839] dib0700: Unknown
> remote controller key: 18 7C 1 0
> Feb 20 22:07:10 matthew-desktop kernel: [38162.906413] dib0700: Unknown
> remote controller key: 18 7C 1 0
> Feb 20 22:07:14 matthew-desktop kernel: [38165.183338] dib0700: Unknown
> remote controller key: 1C 4D 1 0
> Feb 20 22:07:18 matthew-desktop kernel: [38167.156040] dib0700: Unknown
> remote controller key: 1F 7D 1 0
> Feb 20 22:07:21 matthew-desktop kernel: [38168.598632] dib0700: Unknown
> remote controller key: 19 43 1 0
>
> This is very annoying because it seems that polling the syslog every 150ms
> might even give you something if you could work it out ;) Anyway.. any ideas
> where to now...?
you were trying to make a hauppauge remote work. As far as I can see
from this output and from dib0700 code your remote is not supported,
hence there is no keymap hardcoded for it, hence the drivers outputs
"unknow key" since it really doesn't know what to do with the key
received.
Looking at your log it seems even that your remote is not an rc5
standard one since the toggle bit is always set to 1. Please try to
press the same key many times (do not hold it down) and look if the
unknown key is always the same and if the 3rd value changes
alternatively from 0 to 1. If everything is ok you can start to take
note of the values outputed by your keys and try to add a keymap on
your own or send the results here. Note that if toggle bit is not
working properly it the repeat feature would not work perfectly.
I cannot do anything more since I don't have that remote control to
make some test.
Filippo
Hmm...
Maybe you can make more sense of this - the is the result of pressing the same key repeatedly very rapidly (ie as fast as i can ;) )
Feb 20 22:39:48 matthew-desktop kernel: [39332.403671] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:48 matthew-desktop kernel: [39332.555469] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:48 matthew-desktop kernel: [39332.631930] dib0700: Unknown remote controller key: 1F A 1 0
Feb 20 22:39:48 matthew-desktop kernel: [39332.707392] dib0700: Unknown remote controller key: F 39 0 0
Feb 20 22:39:48 matthew-desktop kernel: [39332.783229] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:49 matthew-desktop kernel: [39332.859565] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:49 matthew-desktop kernel: [39333.010863] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:49 matthew-desktop kernel: [39333.086825] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:49 matthew-desktop kernel: [39333.238810] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:49 matthew-desktop kernel: [39333.315022] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:50 matthew-desktop kernel: [39333.390859] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:50 matthew-desktop kernel: [39333.542656] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:50 matthew-desktop kernel: [39333.618559] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:50 matthew-desktop kernel: [39333.694392] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:51 matthew-desktop kernel: [39333.846254] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:51 matthew-desktop kernel: [39333.922152] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:51 matthew-desktop kernel: [39333.998053] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:51 matthew-desktop kernel: [39334.149849] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:51 matthew-desktop kernel: [39334.225750] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:51 matthew-desktop kernel: [39334.301647] dib0700: Unknown remote controller key: 1F A 1 0
Feb 20 22:39:52 matthew-desktop kernel: [39334.453384] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:52 matthew-desktop kernel: [39334.529281] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:52 matthew-desktop kernel: [39334.681017] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:53 matthew-desktop kernel: [39334.832815] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:53 matthew-desktop kernel: [39334.908277] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:53 matthew-desktop kernel: [39335.060139] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:53 matthew-desktop kernel: [39335.136473] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:53 matthew-desktop kernel: [39335.211810] dib0700: Unknown remote controller key: 13 7E 1 0
Feb 20 22:39:54 matthew-desktop kernel: [39335.364108] dib0700: Unknown remote controller key: 13 7E 1 0
Not sure if that's what we were hoping for...
If it's going to help i can write out exactly what keys map to what code...
Cheers,
MAtt
--
Matthew Vermeulen
http://www.matthewv.id.au/
MatthewV @ irc.freenode.net
_______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
