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