Valsecchi Patrick wrote:
Guido Fiala suggested over at the vdr mailinglist initializing the frontend by calling the following every couple seconds helps the situation somewhat: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.
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.html#00457 There's quite some discussion on how to work around this.
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.gzI'll try to find a "budget" card. Seems like those are a bit more stable, isn't it?