From: "Douglas A. Gwyn" <gwyn@arl.army.mil>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Sound cards in use
Date: Fri, 27 Apr 2001 14:40:13 +0000 [thread overview]
Message-ID: <3AE978BE.88FE7BE5@arl.army.mil> (raw)
In-Reply-To: <200104270334.XAA05840@smtp2.fas.harvard.edu>
rsc@plan9.bell-labs.com wrote:
> cards seem to be ESS something-or-other, and getting
> documentation out of them is nearly impossible (in some
> cases, they don't even _have_ documentation internally:
> they bought up the company making the chips and it got
> lost in the shuffle or something).
But *some*body must have documentation, since drivers
keep appearing for other systems. Maybe this is a bit
like the vintage computer market in that there is
information out there in private hands, and it just
takes some (human) networking to find it.
next prev parent reply other threads:[~2001-04-27 14:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-27 3:34 rsc
2001-04-27 14:40 ` Douglas A. Gwyn [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-28 14:19 Richard Miller
2001-04-27 7:08 forsyth
2001-04-30 9:24 ` Audible Meowbot
2001-04-26 18:46 nemo
2001-04-26 16:32 matt
2001-04-26 17:57 ` Dan Cross
2001-04-27 9:12 ` Douglas A. Gwyn
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=3AE978BE.88FE7BE5@arl.army.mil \
--to=gwyn@arl.army.mil \
--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).