From: Bob McElrath <rsmcelrath@students.wisc.edu>
To: Jeff Golds <jgolds@resilience.com>
Cc: Wakko Warner <wakko@animx.eu.org>,
Pierfrancesco Caci <p.caci@seabone.net>,
linux-kernel@vger.kernel.org
Subject: Re: es1371 and recent kernels
Date: Tue, 12 Jun 2001 16:31:50 -0500 [thread overview]
Message-ID: <20010612163150.C16885@draal.physics.wisc.edu> (raw)
In-Reply-To: <873d95lnqr.fsf@paperino.int-seabone.net> <20010612111503.A870@draal.physics.wisc.edu> <20010612164204.A21504@animx.eu.org> <3B2681A8.567992F6@resilience.com>
In-Reply-To: <3B2681A8.567992F6@resilience.com>; from jgolds@resilience.com on Tue, Jun 12, 2001 at 01:55:04PM -0700
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
Jeff Golds [jgolds@resilience.com] wrote:
> Wakko Warner wrote:
> >
> > My ES1370 has done me good. You might want to try that card. Yes it's a
> > creative card. It only has a crackle running 22k 8-bit
> >
>
> It's probably better because that is the AudioPCI chip from Ensoniq
> before Creative bought them. I thought that was a good chip, too.
Argh, I had one of those, gave it away because it would hang my alpha
hard (I'm told the card is pretty nonconformant to the PCI spec).
*sigh*
Nobody out there uses a non-Create PCI card? (oh and not Aureal either)
Cheers,
-- Bob
Bob McElrath (rsmcelrath@students.wisc.edu)
Univ. of Wisconsin at Madison, Department of Physics
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2001-06-12 21:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 15:30 Pierfrancesco Caci
2001-06-12 15:53 ` Luigi Genoni
2001-06-12 16:15 ` Bob McElrath
2001-06-12 20:42 ` Wakko Warner
2001-06-12 20:55 ` Jeff Golds
2001-06-12 21:31 ` Bob McElrath [this message]
2001-06-12 21:43 ` Jeff Garzik
2001-06-12 21:55 ` Wakko Warner
2001-06-12 21:47 ` David S. Miller
2001-06-12 17:05 ` James Stevenson
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=20010612163150.C16885@draal.physics.wisc.edu \
--to=rsmcelrath@students.wisc.edu \
--cc=jgolds@resilience.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.caci@seabone.net \
--cc=wakko@animx.eu.org \
/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
all inboxes | Powered by JetHome®