Now that I understand better... On Sun, Jun 12, 2016 at 01:01:35AM +0200, Henrik Austad wrote: > Userspace is supposed to reserve bandwidth, find StreamID etc. > > To use as a Talker: > > mkdir /config/tsn/test/eth0/talker > cd /config/tsn/test/eth0/talker > echo 65535 > buffer_size > echo 08:00:27:08:9f:c3 > remote_mac > echo 42 > stream_id > echo alsa > enabled This is exactly why configfs is the wrong interface. If you implement the AVB device in alsa-lib user space, then you can handle the reservations, configuration, UDP sockets, etc, in a way transparent to the aplay program. Heck, if done properly, your layer could discover the AVB nodes in the network and present each one as a separate device... Thanks, Richard -- To unsubscribe from this list: send the line "unsubscribe alsa-devel" in _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
