From: Paul Davis <pbd@op.net>
To: Reynald Hoskinson <bean@openface.ca>
Cc: alsa-devel@alsa-project.org
Subject: Re: any change in usb status?
Date: Mon, 04 Mar 2002 12:12:57 -0500 [thread overview]
Message-ID: <200203042212.RAA03293@renoir.op.net> (raw)
In-Reply-To: Your message of "Mon, 04 Mar 2002 12:52:56 PST." <3C83DEA8.6010000@openface.ca>
>I'm eying the maudio USB Audio Duo. It seems an ideal soundcard for my
>needs, is locally available, and relatively inexpensive, and if I ever
>get a laptop, it'll work with that too. I understand usb is not
>supported by alsa yet. Is this still true? Is there plans for the
>future, or is there something that makes it impossible ever to use with
>alsa? The m-audio delta series is well supported, so perhaps this could
>be too in the future?
as i noted the other day, i believe that the plan is to support USB
(and IEEE1394/firewire) entirely in user space, though with the help
of the existing (generic) USB/IEEE1394 drivers.
alsa-lib has been designed to support such things. you just write a
library that opens the relevant USB device, handles the protocol
translation, and provides the functions used by alsa-lib. there is no
need to write a kernel driver. however, i have not heard of any plans
by anyone to do this. its not that hard in theory, but the impression
i have is that very few USB devices are fully standards-compliant, so
there is kinds of futzing around to get the device-specific parts of
the protocol translation part to work 100%.
--p
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
prev parent reply other threads:[~2002-03-04 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 20:52 any change in usb status? Reynald Hoskinson
2002-03-04 17:12 ` Paul Davis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200203042212.RAA03293@renoir.op.net \
--to=pbd@op.net \
--cc=alsa-devel@alsa-project.org \
--cc=bean@openface.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.