mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-12-14 08:56:37 -05:00
4288a634f4
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. |
||
|---|---|---|
| .. | ||
| meson.build | ||
| stress-ringbuffer.c | ||
| test-graph.c | ||
| test-graph2.c | ||
| test-mixer.c | ||
| test-perf.c | ||
| test-props.c | ||
| test-props2.c | ||
| test-props4.c | ||
| test-props5.c | ||
| test-ringbuffer.c | ||
| test-v4l2.c | ||