search

aesr-lab / linux-avb-driver

linux AVB ALSA driver
7 stars 1 forks source link

Connection management insufficient #1

Open grrrr opened 11 months ago

grrrr commented 11 months ago

Currently, upon connected a stream, e.g. from RME Digiface AVB to the ALSA AVB driver, hive will show the connection, but in a "red", that is defunct state.

It seems that upon a connection request (AVB_ACMP_MSGTYPE_CONNECT_RX_CMD), the driver as a listener not only has to respond with a AVB_ACMP_MSGTYPE_CONNECT_RX_RESP response (which it does), but must also send a AVB_ACMP_MSGTYPE_CONNECT_TX_CMD command, which again should be answered with AVB_ACMP_MSGTYPE_CONNECT_TX_RESP by the talker.

In wireshark one can observe that sequence with working AVB devices using a ieee1722.subtype == 0xfc filter.

grrrr commented 11 months ago

Obiously, apart from the message type and the sequence id, all the data are the same between AVB_ACMP_MSGTYPE_CONNECT_RX_CMD/AVB_ACMP_MSGTYPE_CONNECT_RX_RESP and AVB_ACMP_MSGTYPE_CONNECT_TX_CMD messages.

The order, whether AVB_ACMP_MSGTYPE_CONNECT_TX_CMD or AVB_ACMP_MSGTYPE_CONNECT_RX_RESP is sent first, doesn't seem to matter.