* [linux-dvb] Nova-T-500 Remote & dvb-usb-dib0700-1.20.fw
@ 2008-10-10 11:30 Public Email
0 siblings, 0 replies; 2+ messages in thread
From: Public Email @ 2008-10-10 11:30 UTC (permalink / raw)
To: linux-dvb
Hi. I have just updated to the new firmware and updated the v4l-dvb
drivers, installed the new modules and done a cold boot.
Everything is working nicely except for the remote. Pressing any key
once results in constant key repeats. Killing lircd and restarting it
doesn't stop them (it just carries on repeating the key that was
pressed before killing lircd). It isn't the remote as removing the
battery has no effect.
It all worked fine with dvb-usb-dib0700-1.10.fw
Also dmesg is still being flooded with "dib0700: Unknown remote
controller key:" with both firmwares and the latest drivers and there
are several "dtv_property_cache_sync()" appearing every 5 mins too.
I am using gentoo with 2.6.24-tuxonice-r9 kernel.
Thanks
Alex
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [linux-dvb] Nova-T-500 Remote & dvb-usb-dib0700-1.20.fw
@ 2008-10-12 20:32 Risto Pajula
0 siblings, 0 replies; 2+ messages in thread
From: Risto Pajula @ 2008-10-12 20:32 UTC (permalink / raw)
To: linux-dvb
Hello.
I can confirm the problem reported in the email:
http://www.linuxtv.org/pipermail/linux-dvb/2008-October/029625.html
I tested using the v4l-dvb mercurial from today and when
dvb-usb-dib0700-1.20.fw is used the remote always repeats the last
pressed key until the another key is pressed. If I use the same v4l-dvb
drivers and the dvb-usb-dib0700-1.10.fw the remote works just fine. The
cold boot is required between the tests to see any difference.
However I can not get any "dib0700: Unknown remote controller key:" but
dtv_property_cache_sync() appears in few minutes in the dmesg.
My system is:
Suse 11.0 2.6.25.16-0.1-default x86_64
I looked at the code and by making a lot of assumptions.... ;) I guess
the call to the dib0700_rc_setup() from the dib0700_rc_query() wont
erase the last IR code from the chip anymore if the new firmware is
used...? However I really don't have idea how to fix it.. I would be
happy to test anything if you have some suggestions.
BR.
Risto Pajula
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-10-12 20:33 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-10-12 20:32 [linux-dvb] Nova-T-500 Remote & dvb-usb-dib0700-1.20.fw Risto Pajula
-- strict thread matches above, loose matches on Subject: below --
2008-10-10 11:30 Public Email
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox