Hi Patrick, On Sun, 26 Jun 2005, Patrick Boettcher wrote: > Hi, > > On Sun, 26 Jun 2005, Andrew Hodgson wrote: > > Thanks for you quick reply. Attached are the diffs for a800.c and > > dvb-usb-remote.c. The changes to a800.c are trivial just a few errors > > in the remote control codes. > > > The other change was to make auto repeat work. Hope this helps and > > thanks for the great work. The dvb-usb box works wonderfully better > > than the PCI card which always had overheating problems > > Yeah. After you saying you found bugs in dvb-usb-remote.c I had a look > for myself and found them, too. > I have a shuttle sb61g2 with a Nova-T DVB-T PCI card (the one with the grey remote) and an AVerMedia AverTV DVB-T USB 2.0 (A800). It looks like budget-ci.c module has problems similar to the a800 with auto repeat. A colleague of mine made some changes to the code to allow better handling of the repeats and I've been manually applying his changes each time I grab code from CVS. I'm no driver coder so I don't fully understand what his changes entail or whether they make sense for all supported remotes, however it does make my grey hauppauge remote work wonderfully well. His method of selecting the keycodes was via a simple hash define (might be better using a module parameter IMHO). Anyway I just thought I'd send you the diffs to let you see them. This is for my Hauppauage Nova-T DVB-T card. As I said, I also have a AVerMedia AverTV DVB-T USB 2.0 (A800) so I'm looking forward to any fixes for it's remote making their way into CVS. The other thing I've noticed with my a800 is that tzap works flawlessly with great quality, but when I use it with MythTV 0.18.1 it often fails to get FE_LOCK or the picture is very garbled. The Nova-T using the same antenna and tzap has no problems with either card. Is there any reason tzap would work while MythTV has issues ? Any thoughts much appreciated. -- Doug Scoular "The big print giveth and the UNIX Systems Architect small print taketh away" D: +61 2 8446 6035 M: +61 402 896747 E: dscoular@xxxxxxxxx