From: Sape Mullender <sape@plan9.bell-labs.com>
From: sape@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sound question
Date: Sat, 28 Jun 2003 12:06:32 -0400 [thread overview]
Message-ID: <e30f7542dc8bef7007f106d28ae28e1c@plan9.bell-labs.com> (raw)
In-Reply-To: <03062812093900.00512@localhost.localdomain>
> could you tell me what exactly USB audio cards do you use?
USB audio devices usually conform to the USB standard for
audio. The Plan 9 driver can drive such devices. There are
a few (usually high end) audio devices that deviate from the
standard and require a vendor-specific driver.
Audio devices that can be driven by WIndows without installing
a driver from the manufacturer should be okay for Plan 9.
I have tested the driver on Philips USB speakers, Edirol UA-3 Audio
interface, Xitel AN1 and MD.
Sape
next prev parent reply other threads:[~2003-06-28 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-28 16:09 Andrey S. Kukhar
2003-06-28 16:06 ` Sape Mullender, sape [this message]
2003-06-28 16:37 ` David Presotto
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=e30f7542dc8bef7007f106d28ae28e1c@plan9.bell-labs.com \
--to=sape@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).