Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Tony Nugent <Tony.Nugent@usq.edu.au>
To: linux-sound@vger.kernel.org
Subject: Re: Question:ESS Sound Card
Date: Sun, 25 Oct 1998 05:57:09 +0000	[thread overview]
Message-ID: <marc-linux-sound-90938936816466@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-90925336113724@msgid-missing>

On Sat Oct 24 1998 12:10, Stuart Felenstein wrote:

> I have a sound card, manufacturer Shark.  I don't really have much specs
> on it, well I know it's 16bit.
> The driver is ESS1681.  I'm wondering what kind of problems I'll
> encounter and if it's at all possible to even get this card working.

In my experiences with the 18xx series, the ESS chips are a cheap and nasty
SBPro clone.  (No flames please... this is just IMHO).

The only reason I used one for so long was the ability to run an old
Panasonic 2x drive off it on the /dev/sbpcd device.

> I'll probably try the OSS (4 Front) drivers since they seem the most
> stable , at least from what I've read.
> 
> Anyone ever tried this type of card? Any suggestions?  Any help?

The OSS (commercial/time-limited trial) drivers detected the ESS chip I
had, and loaded a specific driver for it.  But I never did get the full
(unlimited) driver for it, since the SB driver in the kernel seemed to work
just as well with it (and the kernels were changing versions quite a bit at
the time... a real hassle to upgrade the OSS drivers all the time).

I'm not so familiar with the 1681 chip (err, not at all actually), so your
milage may vary.  (I'll never touch them again, btw).

Cheers
Tony

  reply	other threads:[~1998-10-25  5:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-24 17:10 Question:ESS Sound Card Stuart Felenstein
1998-10-25  5:57 ` Tony Nugent [this message]
1998-10-26  2:41 ` Bill Nottingham

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=marc-linux-sound-90938936816466@msgid-missing \
    --to=tony.nugent@usq.edu.au \
    --cc=linux-sound@vger.kernel.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