Hi Shaun,
Shaun Jackman wrote:
Just wanted to report this works great with my FlyVIDEO2000, which
has a RM-050 remote control. Thanks for your excellent work!
I noticed something strange when testing it with irw. The
remote never produces more than six repetitions of a button, then
stops, and starts over. This is probably more easily shown with a
dump of irw:
000000000000001b 00 MUTE lircd.conf.fly3k
000000000000001b 01 MUTE lircd.conf.fly3k
000000000000001b 02 MUTE lircd.conf.fly3k
000000000000001b 03 MUTE lircd.conf.fly3k
000000000000001b 04 MUTE lircd.conf.fly3k
000000000000001b 05 MUTE lircd.conf.fly3k
000000000000001b 06 MUTE lircd.conf.fly3k
000000000000001b 00 MUTE lircd.conf.fly3k
000000000000001b 01 MUTE lircd.conf.fly3k
000000000000001b 02 MUTE lircd.conf.fly3k
000000000000001b 03 MUTE lircd.conf.fly3k
000000000000001b 04 MUTE lircd.conf.fly3k
000000000000001b 05 MUTE lircd.conf.fly3k
000000000000001b 00 MUTE lircd.conf.fly3k
This causes buttons like mute that shouldn't repeat, to repeat. Is
this is a hardware limitation (some funky key repeat built into the
remote), or a software artifact?
Probably a software artifact due to the fact the gpio register is
polled. This has been fixed in the latest version, which uses interrupts
instead of polling, available here:
http://users.tpg.com.au/atko/gpf/ir/
Note that it freezes when you try to unload the LIRC module.
Now a couple comments on naming. Since this is working, and quite
well!, let's get into the upstream sources. lirc_gpio_s should be
renamed to lirc_saa7134 (like Steven suggested). I think the remote
should be named after the remote, and not the card. I don't own a
FV3k so naming the remote fly3k makes no sense for me. The remote I
have is labelled RM-050; I would use that name.
Thanks!
Shaun
I've renamed it, however I wouldn't be surprised if there were TV cards
using the SAA713x that don't use the GPIO register for remotes.
The freezing bug probably ought to be fixed before I try and get it
upstream *g*.
- David.
