pipewire/src
Wim Taymans f8663ab31c client-node: activate using the node eventfd
Don't make an extra eventfd for activating the remote-node, we can
use the server side eventfd and send them to the remote side using
the transport.

The remote node already adds the eventfd to the data-loop so avoids
doing the same on the server.

This makes driver nodes trigger all remote nodes directly instead of
going through an intermediate eventfd. For resuming nodes, we already
used the node eventfd directly so this only a small optimization
for the initial cycle start.
2023-05-02 18:47:10 +02:00
..
daemon jack: Add jack.max-client-ports config option 2023-04-21 15:42:57 +02:00
examples core: add bound_props event 2023-03-21 17:22:27 +01:00
gst gst/pipewiresrc: Let GstBaseSrc handle pseudo-live calculations 2023-04-19 19:22:24 +00:00
modules client-node: activate using the node eventfd 2023-05-02 18:47:10 +02:00
pipewire client-node: activate using the node eventfd 2023-05-02 18:47:10 +02:00
tests core: add bound_props event 2023-03-21 17:22:27 +01:00
tools pw-config: fix include for isatty 2023-04-20 10:40:47 +02:00
meson.build treewide: meson.build: use feature.allowed() 2022-02-04 00:15:59 +01:00