> isn't it possible to use the generic ringbuffer implementation for these > purposes (maybe it has to change a little - but this should not be a > real problem - )?
actually that's the current implementation, just my ringbuffer is 'infinite' I mean longer than the maximum expected section data because complete sections must never wrap around otherwise we'll have to memcopy again which we must do not on cpu tight systems. Chasing pointers of the ringbuffer are tsfeedp (front writer) and secbufp (back reader). -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
