[linux-dvb] T200 Remote Oddities

Ben Griffiths b.tgriff at tiscali.co.uk
Thu Oct 27 23:44:35 CEST 2005


On Wednesday 26 October 2005 02:26, Poulter, Nicholas wrote:
> On Tuesday 25 October 2005 00:33, Andy wrote:
> > > Has anyone else had anything like this.
> >
> > Yes, my remote has always been dodgy yet haven't had the time to play
>
> with
>
> > it too much. As far as I can tell, all the keypresses lag by one
>
> keypress,
>
> > e.g., if I press UP, DOWN, LEFT, RIGHT, UP, MENU, DOWN, the following
> > actions happen: <nothing>, UP, DOWN, LEFT, RIGHT, UP, MENU.
> >
> > This behaviour is in mythtv; like I said I haven't had much time to
>
> play
>
> > with irw to see exactly what's happening, hopefully some time soon
>
> though!
>
> > Please post any updates to the list, and I'm happy to test any code
>
> fixes
>
> > you develop!
> >
> > Good luck!
> >
> > Andy
> >
> >I don't see it that clear cut. Sometimes it will work perfectly but
>
> then >after
>
> >20-30 key presses I start getting the phantom key presses - but they do
> >only
> >occur when I press a button.
> >
> >Unfortunately I won't be able to help out on the coding front I was
>
> just
>
> >wondering whether it was limited to me.
> >
> >Ben
>
> What happens when you don't have LIRC loaded? The remote will work just
> like a keyboard. What you can do is get the DVB-TOOLS package from
> linuxtv.org and compile the program evdev
>
> Then you can do the following
>
> evdev /dev/input/event(x) where (x) is your event id of your device.
> This will give you the keypress's that the remote is sending. If the
> issue you are having does not occur when you do this then the problem
> will be with lirc. If it does occur then it could be that something is
> interfering with the remotes reception causing it not to interpret the
> button releases.

I can't find this program can you give me a pointer.
>
> I don't seem to have any problems with my DVB-T300. Is there anything
> near your remote receiver that could be causing interference at all?
>
> If you tail you dmesg you'll see something along the following
>
> mythbox kernel: saa7134[0]/ir: build_key gpio=0x940f00 mask=0x0 data=0
> mythbox kernel: saa7134[0]/ir: build_key gpio=0x800200 mask=0x0 data=0
> mythbox kernel: saa7134[0]/ir: build_key gpio=0x940200 mask=0x0 data=0
> mythbox kernel: saa7134[0]/ir: build_key gpio=0x800700 mask=0x0 data=0
> mythbox kernel: saa7134[0]/ir: build_key gpio=0x940700 mask=0x0 data=0
>
> If you could give me a capture of what's happening I'll take a look.

I couldn't find the output above in my output from dmesg. This is what I got,

Oct 27 20:07:20 marty kernel: saa7130[0]: found at 0000:00:0b.0, rev: 1, irq: 
177, latency: 32, mmio: 0xe5000000
Oct 27 20:07:20 marty kernel: saa7130[0]: subsystem: 185b:c901, board: Compro 
Videomate DVB-T200 [card=71,autodetected]
Oct 27 20:07:20 marty kernel: saa7130[0]: board init: gpio is 841100
Oct 27 20:07:20 marty kernel: saa7130[0]: registered input device for IR
Oct 27 20:07:20 marty kernel: saa7130[0]: i2c eeprom 00: 5b 18 01 c9 54 20 1c 
00 43 43 a9 1c 55 d2 b2 92
Oct 27 20:07:20 marty kernel: saa7130[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff 
ff ff ff ff ff ff ff ff ff
Oct 27 20:07:20 marty kernel: saa7130[0]: i2c eeprom 20: 01 40 01 03 03 ff 03 
01 08 ff 00 88 ff ff ff ff
Oct 27 20:07:20 marty kernel: saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff 
ff ff ff ff ff ff ff ff ff
Oct 27 20:07:20 marty kernel: saa7130[0]: i2c eeprom 40: ff d0 00 c2 86 10 ff 
ff ff ff ff ff ff ff ff ff
Oct 27 20:07:20 marty kernel: saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff 
ff ff ff ff ff ff ff ff cb
Oct 27 20:07:20 marty kernel: saa7130[0]: i2c eeprom 60: 30 26 ff ff ff ff ff 
ff ff ff ff ff ff ff ff ff
Oct 27 20:07:20 marty kernel: saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff 
ff ff ff ff ff ff ff ff ff
Oct 27 20:07:20 marty kernel: saa7130[0]: registered device video0 [v4l2]
Oct 27 20:07:20 marty kernel: saa7130[0]: registered device vbi0
Oct 27 20:07:20 marty kernel: DVB: registering new adapter (saa7130[0]).
Oct 27 20:07:20 marty kernel: DVB: registering frontend 0 (Philips TDA10046H 
DVB-T)...
>
> I don't have a T200 so it's hard to test and that was put in as the T200
> and T300 are so similar. However if the issue is happening with a T300
> then I'll be able to do some tests and see. But if you could give me the
> captures from dmesg and from evdev that would be great.
>
> Cheers
>
> Nick
>
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb at linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

I did a bit more testing using a text editor after closing lircd. I basically 
tried inputing numbers from the keypad as though it were a keyboard and still 
got the same behaviour so I don't think it's limited to lirc. 

Thanks,

Ben



More information about the linux-dvb mailing list