[vdr] Re: Experiences with patched VDR 1.2.x (was Re: [PATCH] Old descriptorh

["Christian Jacobsen" <christian.jacobsen@stageholding.de>]

Hallo,

>No let us assume that someone have 4 cards. With your idea, this guy
>wouldn't be able to tune to 3 transponders in live view. Maybe it is
>possible to
>start a transfer mode whenever a transponder is needed, to which one of
>card 2-4
>is switched. But what about recording? 


If I understand it right then it is only a problem with 2 cards sitting
next to each others !
This means that card 1 and 2 should not use same transponder, on 1 and 3
it should be OK to use the same. Then again 2 and 3 should not use same
transponder and so on.

>
>Hmm, I think we should track this error on its root. I'd a look in DVB-CVS
>and noticed that in mid-june 2002 there was a change in the mentioned
>function. Maybe we should try the older version of that function?


I am not sure which change you mean. Could you point me to it :
http://linuxtv.org/cgi-bin/cvsweb.cgi/DVB/driver/dvb_frontend.c

I will then try without that change.


>Until now, we've no idea, why this error occur only on the secondary card.
>When I understand the text above correctly, this behaviour should occur on
>both cards at the same time. But this isn't the case. 


Yes you are right here. It says "so both lose sync" - hmm.
But I think it is worth trying anything that could work. And as it seems
to be a driver bug which vdr triggers with the 1.1.27c patch, or am I
wrong here.
(hw_sections=1 also goes in that direction.)

>
>And why is it impossible to tune to any channel on the secondary card,
>when
>this behaviour occur? Only a restart of the driver helped.


That also "points" to the Driver.
>
Greetings
Christian Jacobsen



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