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
..
alsa-monitor.c	update docs	2017-11-13 19:58:52 +01:00
alsa-sink.c	cleanups	2017-11-20 15:26:44 +01:00
alsa-source.c	cleanups	2017-11-20 15:26:44 +01:00
alsa-utils.c	buffer: don't use ringbuffer in chunk	2017-11-21 12:42:27 +01:00
alsa-utils.h	buffer: don't use ringbuffer in chunk	2017-11-21 12:42:27 +01:00
alsa.c	Use errno for result errors	2017-11-13 09:41:41 +01:00
meson.build	Don't hardcode plugin path	2017-06-19 12:19:22 +02:00