Andrew de Quincey wrote: > > > I do not know the protocol well enough, to see the problem, but I think it > > has something todo with a tcid comparison in cam_set which is not > > fulfilled. The second possible problem I see is that the > > dvb_ca_en50221_read_data function is called 1130 times in 12 seconds, but > > no data is delivered to cam_set after the 7 bytes. > > > > I have also seen one time, that every io_poll returned with a time out, > > also the one after the FR IRQ. And so cam_set never called read and > > returned errors only. But I have no log of this and I have no access to the > > machine anymore, because it crashed. > > > > I started cam_set, killed it with CTRL+C somewhere between write and read > > call and started it again. After this procedure the connection was lost. > > > > I hope this will help a little bit, I will continue my tests after I have > > reseted the machine today evening or tomorrow. > > Thanks very much, I'm hopefully about to start testing this stuff myself soon. > > Are you using the very latest CVS? I found and fixed a stupid bug yesterday > which would explain why dvb_ca_en50221_read_data is called 1130 times in only > a few seconds.
Since AFAIK the CI code in libdvb originally came from VDR I would appreciate if you could send me a copy of any fixes you make to that code. Klaus -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
