Skip to contentSkip to conversation

USB Quattro Linux support

DISCUSSION Patrick Shirkey 2 participants 2 messages Apr 15, 2002

lore
Share & tools
lore
#0 lore raw
Quoted 18 lines · --- James Tappin
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-driver

the 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 10 lines

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.

I think that there is support in gphoto for capturing video streams but I haven't used it so I don't know if that is correct. Anyway if I am correct then latency issues would have been solved already.

I will query with someone from their list and report back unless someone else knows for certain.

--
Patrick Shirkey - Boost Hardware Ltd
For the discerning hardware connoisseur Http://www.boosthardware.com Http://www.boosthardware.com/LAU/Linux_Audio_Users_Guide/

Quoted 11 lines
Signature · 10 lines
+------------------------+-------------------------------+---------+
| James Tappin           | School of Physics & Astronomy |  O__    |
| [email protected] | University of Birmingham      | --  \/` |
| Ph: 0121-414-6462. Fax: 0121-414-3722                  |         |
+--------------------------------------------------------+---------+

_______________________________________________
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

#1 lore raw
Quoted 8 lines
Quoted 8 lines

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.

If usb-lib is written properly and low-level-generic-USB-driver is written correctly, there are no latency issues. Latency issues don't arise from the number of layers of code unless one of the layers of code is astonishingly badly written. They arise from designs that buffer data along the way or delay execution of a thread. The system outlined above doesn't inherently have any such problems.

Quoted 3 lines

I think that there is support in gphoto for capturing video streams but I have n't used it so I don't know if that is correct. Anyway if I am correct then la tency issues would have been solved already.

Not at all. arecord(1) can capture audio, but it can't capture 26 channels of audio at 64 frames/interrupt. Handling latency is partly an application issue, partly a kernel issue, and partly a requirement that libraries in the way don't get in the way. It has very little to do with whether you can do certain generic tasks or not.

--p