Dev-Daemon

From Tuxisalive

First software suite : out of date This article is related to the first software architecture. It's now out of date, but kept in this wiki for your information.

TODO

#1 Use the GNU Autotools framework to configure and compile the daemon

#2 Support multiple dongles

Right now it's impossible to connect 2 tux to the same computer. We could either add multiple dongle support in the daemon or being able to start one sub-daemon per tux.

#3 Detection of the corresponding audio device.

When the daemon opens a usb connection to a dongle, it only opens the command interface. The audio interface is addressed directly by the applications. We want the daemon to find which is the corresponding audio interface device, no matter if other dongles or usb audio devices are plugged. That device should be accessible by the API. It should be possible to retrieve the alsa device name from /proc/asound/cards, then in case multiple dongles are plugged, find the correct one by looking into /proc/asound/cardx/usbbus. There's maybe better way to retrieve that by using the alsa API directly. We should also find the OSS devices if OSS is supported.

Feature suggestions

#1 SNMP Support

Define and implement a MIB for tux. This would mean enabling a snmp agent to send tcp commands to the daemon.