[linux-dvb] Re: stability problems + closing and re-opening the frontend

["Valsecchi Patrick" <patrick.valsecchi@nagra.com>]

I have a rev2.1. I've put the output of dmesg at the end of that Email.

Tomorrow, I'll try to change my little test software to work with version 0.9.4 of the DVB drivers. We'll see if that changes anything.

---------------
# dmesg
Linux video capture interface: v1.00
saa7146: register extension 'dvb'.
saa7146: found saa7146 @ mem e0915000 (revision 1, irq 10) (0x13c2,0x0003).
DVB: registering new adapter (Technotrend/Hauppauge PCI rev2.1).
Technotrend/Hauppauge PCI rev2.1 adapter 0 has MAC addr = 00:d0:5c:xx:xx:xx
DVB: AV7111(0) - firm f0240009, rtsl b0250018, vid 71010068, app 8000261b
DVB: AV7111(0) - firmware supports CI link layer interface
av7110(0): adac type set to 0
videodev: "av7110" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/
saa7146_vv: saa7146 (0): registered device video0 [v4l2]
av7110: found av7110-0.
probe_tuner: try to attach to Technotrend/Hauppauge PCI rev2.1
drivers/media/dvb/frontends/stv0299.c: setup for tuner BSRU6, TDQB-S00x
DVB: registering frontend 0:0 (STV0299/TSA5059/SL1935 based)...
---------------

> -----Original Message-----
> From: linux-dvb-bounce@linuxtv.org
> [mailto:linux-dvb-bounce@linuxtv.org]On Behalf Of Gregor Lawatscheck
> Sent: Monday, April 05, 2004 5:14 PM
> To: linux-dvb@linuxtv.org
> Subject: [linux-dvb] Re: stability problems + closing and 
> re-opening the
> frontend
> 
> 
> Valsecchi Patrick wrote:
> 
> > Hi,
> > 
> > In my kind of application (monitoring) I don't really care 
> if I loose some packets. Would it be possible to reset the 
> firmware when that happens? That's what I wanted to try to do 
> by closing the firmware and re-opening it.
> 
> Guido Fiala suggested over at the vdr mailinglist initializing the 
> frontend by calling the following every couple seconds helps the 
> situation somewhat:
> ves1x93_init (i2c);
> 
> The reference for this is the following post:
> http://www.linuxtv.org/mailinglists/vdr/2004/03-2004/msg00457.html
> 
> > Maybe when can trigger that reset when the "waiting for 
> command idle" problem appears. Then send back the tune 
> command. That way, we recover the card without manual 
> operations and without the user level to notice it (maybe a 
> slower tune, though). Or, if you guys think it's too radical, 
> maybe add a reset ioctl. That way, the user level can solve 
> the problem by itself.
> 
> Have a look at the whole thread for the reference above:
> http://www.linuxtv.org/mailinglists/vdr/2004/03-2004/threads.h
tml#00457

There's quite some discussion on how to work around this.

> I'll try to find a "budget" card. Seems like those are a bit more stable, isn't it?

It might be worth it if you can try to reproduce this on a 0.9.4 driver 
(the api is slighly different): 
http://www.linuxtv.org/download/dvb/old/siemens_dvb-0.9.4.tar.gz
If not - then there's a good chance this could be fixed.

Later full featured cards (i.e. some rev 1.5, all of rev 1.6 and 2.x) 
seem stable even with the newer drivers if I'm not mistaken. You appear 
to have a revision 1.3 full featured card (driver promts this when the 
modules are loaded).

- Gregor


-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.