USB Quattro Linux support
Quoted 11 lines · --- Paul Davis
Quoted 11 lines
Quoted 11 lines
framework for ALSA worked out, which is even more of a problem. Its still unclear at this point whether the ALSA framework will be:
application<->alsa-lib<->alsa-driver<->low-level-ALSA-USB-class-driverOR
application<->alsa-lib<->low-level-non-ALSA-USB-class-driverthe first one is easier to write, the second one is more flexible.
I think a good example of how ALSA should work with USB devices is the gphoto approach. From what I know of their framework it is along the same lines as the first option.
Quoted 8 lines
the problem i alluded to is just one of making an architectural decision. do you consider USB Audio devices to be best supported by a kernel driver with a USB focus, or an ALSA focus? alsa-lib can handle either, but in the former case (USB focus), more code has to be written in user space, and the existing USB audio driver for OSS has to be moved out of OSS and made more generic.
I'm pretty sure that we would have the means currently to see the device through the usb port. (I'll need to test that out) The problem I see is how does ALSA access the kernels USB modules and once that is sorted out we need the specs for the devices.
So how do we go about writing a "low-level-ALSA-USB-class-driver"?
--
Patrick Shirkey - Boost Hardware Ltd
For the discerning hardware connoisseur Http://www.boosthardware.com Http://www.boosthardware.com/LAU/Linux_Audio_Users_Guide/
Quoted 4 lines
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
_____________________________________________________________
Want a new web-based email account ? ---> http://www.firstlinux.net
_____________________________________________________________
Run a small business? Then you need professional email like [email protected] from Everyone.net http://www.everyone.net?tag
Quoted 9 lines · Patrick Shirkey
Quoted 8 lines · --- Paul Davis
Quoted 8 lines
Quoted 8 lines
framework for ALSA worked out, which is even more of a problem. Its still unclear at this point whether the ALSA framework will be:
application<->alsa-lib<->alsa-driver<->low-level-ALSA-USB-class-driver
OR
Quoted 7 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
application<->alsa-lib<->low-level-non-ALSA-USB-class-driverthe first one is easier to write, the second one is more flexible.
I think a good example of how ALSA should work with USB devices is the gphoto approach. From what I know of their framework it is along the same lines as the first option.
I think a more exact description of the gphoto approach is:
application<->gphoto-lib<->usb-lib<->low-level-generic-USB driver.
Only the low-level kernel USB drivers and the usbdevfs filesystem are in kernel space, beyond that the hardware driving is done via the user-space libusb. I'm not sure whether this would have low-enough latency for audio use, after all, digital cameras aren't timing-critical for the sort of things that gphoto aims to do.
Signature · 5 lines
+------------------------+-------------------------------+---------+ | James Tappin | School of Physics & Astronomy | O__ | | [email protected] | University of Birmingham | -- \/` | | Ph: 0121-414-6462. Fax: 0121-414-3722 | | +--------------------------------------------------------+---------+