Perhaps a plug-in or a setup menu entry to enable the work around code for VDR until the driver has resolved this issue.<br><br>Could this be done as a plugin?<br><br><div><span class="gmail_quote">On 09/04/2008, <b class="gmail_sendername">Tuomas Jormola</b> <<a href="mailto:tjormola@cc.hut.fi">tjormola@cc.hut.fi</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br> On 9 Apr 2008, at 00:26, Klaus Schmidinger wrote:<br> > On 04/08/08 23:17, Tuomas Jormola wrote:<br> >> On 8 Apr 2008, at 23:49, Klaus Schmidinger wrote:<br> >>> Since this apparently happens also without VDR, I guess it will have<br>
>>> to<br> >>> be fixed in the driver.<br> >> Well, the funny thing is that VDR 1.4.7 with exactly the same kernel<br> >> and hardware does not give any symptoms at all. On startup CAM is<br>
>> initialized quickly just fine.<br> ><br> > VDR 1.4 didn't permanently monitor the module status.<br> <br>Well, as an end user I don't really care what the two versions do<br> differently behind the scenes. Net effect for me is that with VDR 1.4<br>
my CAM is working and with VDR 1.6 it's unusable. So to me VDR 1.6 is<br> broken, what ever the technical reason might be.<br> <br><br> Tuomas<br> <br><br> _______________________________________________<br> vdr mailing list<br>
<a href="mailto:vdr@linuxtv.org">vdr@linuxtv.org</a><br> <a href="http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr">http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr</a><br> </blockquote></div><br>