[alsa-devel] US-1641 drivers involvment
Hello, I would participate, if possible, in the ALSA development to add support to the USB card Tascam US-1641. Any reply or help from who tried in this task before is really really appreciated.
Thank you! Bye. LL
Luca Novarini wrote:
I'm writing you to know how can I participate in the growth of ALSA supported card list to include also my current USB audio card, the Tascam US-1641.
bInterfaceClass 255 Vendor Specific Class
A driver for a device with a vendor-specific protocol would require information from the vendor (Karsten?) or reverse engineering.
Regards, Clemens
Thanks Clemens for your fast answer! The vendor (Tascam) said that US-1641 driver are based on an identical concept as US-144 drivers, so far we should proceed in the same fashion I think.... Have you idea where I can find further infos on how US144 drivers works?
Thank again! Regards, LL
2013/8/29 Clemens Ladisch clemens@ladisch.de
Luca Novarini wrote:
I'm writing you to know how can I participate in the growth of ALSA supported card list to include also my current USB audio card, the Tascam US-1641.
bInterfaceClass 255 Vendor Specific ClassA driver for a device with a vendor-specific protocol would require information from the vendor (Karsten?) or reverse engineering.
Regards, Clemens
Hello? No one got any advice where to start?
Thanks again and anyway, LL Il giorno 29/ago/2013 15:57, "Luca Novarini" luca.novarini@gmail.com ha scritto:
Thanks Clemens for your fast answer! The vendor (Tascam) said that US-1641 driver are based on an identical concept as US-144 drivers, so far we should proceed in the same fashion I think.... Have you idea where I can find further infos on how US144 drivers works?
Thank again! Regards, LL
2013/8/29 Clemens Ladisch clemens@ladisch.de
Luca Novarini wrote:
I'm writing you to know how can I participate in the growth of ALSA supported card list to include also my current USB audio card, the Tascam US-1641.
bInterfaceClass 255 Vendor Specific ClassA driver for a device with a vendor-specific protocol would require information from the vendor (Karsten?) or reverse engineering.
Regards, Clemens
On 05.09.2013 14:30, Luca Novarini wrote:
Hello? No one got any advice where to start?
Try to add the USB ID to the exisiting Tascam driver. Than see how far the driver gets in understanding the device's replies to the setup commands.
As Clemens said, you probably need to reverse engineer the Windows driver in order to understand the details in their protocol.
Daniel
participants (3)
-
Clemens Ladisch -
Daniel Mack -
Luca Novarini