Free Firewire Audio Drivers
Hi guys, I'm new Linux user, I tried to download FFADO mixer for my Esi Duafire, but the device is not supported; is there any chance to have the device full supported? Waiting for your reply I thank you in advance.
Thanks for your post.
As per our FAQ question on support levels, "full support" can only be offered on a device if at least one of the FFADO developers has the device and if the project has received sufficient information (usually from the manufacturer) to allow us to code working support. At present neither of these conditions is met, so the chances of this device obtaining "full support" status is low.
Other levels of support are less stringent, although in reality they are all contingent on a developer having a sample device to use for testing and debugging. Unless a sample device were provided by ESI or someone else I can't see support being added for this device to FFADO any time soon. None of the FFADO developers are paid to work on the project and all development is done in our spare time. Furthermore, none of us have the money to go out purchasing interfaces just so they can be supported on the off-chance that someone could make use of it. As a result, we rely on others who do own additional devices to come forward to lend assistance, but obviously this requires some degree of coding ability and a basic knowledge of the operation of the Firewire bus.
We would certainly welcome any coding assistance you might be able to provide to assist in getting this device supported.
To get you started, the first piece of information required is the underlying chipset that the device is based on. This will indicate whether an existing FFADO driver can be tweaked to support the device or whether a completely new driver is required. Closely related to this is the contents of the ConfigROM; fields such as the VendorID and Model are used by FFADO to identify devices. This information can be obtained from gscanbus or from some files under /proc and/or /sys. This information then permits us to determine what the next steps might be. At present our collective knowledge about this device and its underlying architecture is close to zero (hense the "unknown" support status), so any information you may be able to provide would help fill in the gaps.