[linux-dvb] No more data after EBUFFEROVERFLOW

[Ralph Metzler <rjkm@convergence.de>]

Klaus Schmidinger writes:
 > There have been several reports that VDR stops recording after
 > the driver reports an EBUFFEROVERFLOW (which is listed in the log
 > file as "Unknown error 769" since EBUFFEROVERFLOW is only defined 
 > inside the driver's code).
 > 
 > Taking a close look at DVB/driver/dmxdev.c I saw that the 'buffer.error'
 > is initialized to '0' in DmxDevBufferInit(), and later set to various
 > error codes - but NEVER reset to '0'. Apparently this causes the driver 
 > to no longer deliver (useful) data.
 > 
 > Am I missing something?
 > Shouldn't buffer.error be reset at some point?
 > Or must the application (VDR) do something special after receiving
 > EBUFFEROVERFLOW to reset that error condition?

If you look more closely (like a search for "error" in dmxdev), you 
will see that the error is cleared in DmxDevBufferRead() 
after being read.
Most probably the next overflow error already occured before you 
called read() again.


Ralph





-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe linux-dvb" as subject.