Wim Taymans 4288a634f4 buffer: don't use ringbuffer in chunk ... We can't use a ringbuffer on the chunk because it implies the consumer would write to it to update the read position, which we can't do because the chunk is read-only and might even be shared. Go back to offset/size pairs, which can sortof do the same thing if we want later when we keep a non-shared read pointer in the consumer. Keep alsa timestamp around and filled state for future. mmap the input port meta/data/chunk as read-only. Only do clock update requests when asked.		2017-11-21 12:42:27 +01:00
..
debug.c	buffer: don't use ringbuffer in chunk	2017-11-21 12:42:27 +01:00
debug.h	Reorganise SPA tree	2017-11-10 13:36:14 +01:00
meson.build	Implement param filtering	2017-11-09 17:16:54 +01:00
pod.c	pod: first compare, then advance to next item	2017-11-14 16:49:07 +01:00
pod.h	Improve enum_param	2017-11-13 17:57:38 +01:00