On Sat, 2008-08-23 at 18:20 +0200, Hans Verkuil wrote: > On Saturday 23 August 2008 17:52:05 Andy Walls wrote: > > So without asking the CX23418 to release the MDLs at the end of a > > capture, the CX23418 can later return a data buffer with a buffer id > > in the wrong range for a stream type. cx18_queue_get_buf_irq() will > > gripe when this happens and the data in that buffer will be wrongly > > dropped. > > > > In cx23418.h, CX18_CPU_DE_ReleaseMDL is commented out. Is there a > > problem with it, or is it OK to uncomment and use? > > I was never certain whether is was needed or not. The driver code I have > didn't use it and the documentation is for all practical purposes > non-existent. By all means, see if it fixes this issue. It was always > my impression that the cx23418 automatically released all MDLs after > the capture was stopped and the task destroyed. But I probably never > have tested this particular scenario.
I can't get it to happen, but Brandon did: [65288.817420] cx18-0: Cannot find buffer 58 for stream TS [65288.817440] cx18-0: Could not find buf 58 for stream TS [65840.130797] cx18-0: Cannot find buffer 17 for stream TS [65840.130797] cx18-0: Could not find buf 17 for stream TS [65861.882721] cx18-0: Cannot find buffer 48 for stream TS [65861.882741] cx18-0: Could not find buf 48 for stream TS [66151.627392] cx18-0: Cannot find buffer 107 for stream encoder MPEG [66151.627392] cx18-0: Could not find buf 107 for stream encoder MPEG [67632.953680] cx18-0: Cannot find buffer 99 for stream encoder MPEG [67632.953680] cx18-0: Could not find buf 99 for stream encoder MPEG [67795.527911] cx18-0: Cannot find buffer 106 for stream encoder MPEG [67795.527911] cx18-0: Could not find buf 106 for stream encoder MPEG Note the buffer id's are in the wrong range for the stream types Regards, Andy > Regards, > > Hans > > > > > Regards, > > Andy > > _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
