remote-node: first run the tee and then signal ready

We first need to run the tee so that all the io areas are ready before
we can start the driver on the daemon.
This commit is contained in:
Wim Taymans 2019-03-07 18:34:39 +01:00
parent e31f1fcdca
commit 264383cdd4

View file

@ -1176,11 +1176,15 @@ static int node_ready(void *d, int status)
{ {
struct node_data *data = d; struct node_data *data = d;
struct pw_node *node = data->node; struct pw_node *node = data->node;
struct pw_port *p;
uint64_t cmd = 1; uint64_t cmd = 1;
pw_log_trace("node %p: ready driver:%d exported:%d status:%d", node, pw_log_trace("node %p: ready driver:%d exported:%d status:%d", node,
node->driver, node->exported, status); node->driver, node->exported, status);
spa_list_for_each(p, &node->rt.output_mix, rt.node_link)
spa_node_process(p->mix);
if (write(data->rtwritefd, &cmd, sizeof(cmd)) != sizeof(cmd)) if (write(data->rtwritefd, &cmd, sizeof(cmd)) != sizeof(cmd))
pw_log_warn("node %p: write failed %m", node); pw_log_warn("node %p: write failed %m", node);