Linux Sound subsystem development
 help / color / mirror / Atom feed
To: linux-sound@vger.kernel.org
Subject: Re: Ensoniq AudioPCI problem solved
Date: Tue, 18 Jul 2000 11:38:08 +0000	[thread overview]
Message-ID: <marc-linux-sound-96394415130517@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-96384437322596@msgid-missing>

hello dan !

nice to hear you have sound going now !

Dan Lasley wrote:
> 
> In a recent posting, I asked if anyone knew why Red Hat 6.0 couldn't
> see and configure my Ensoniq AudioPCI sound card.  A number of
> respondents suggested I load the ALSA sound drivers
> (http://www.alsa-project.org/).
> 
> I thanked everyone who responded (except jay@toltec.metran.cx, who I
> could not reach via e-mail).
> 
> The ALSA code worked, but eLinux.com, the vendor who sold the AudioPCI
> card, had a better solution:

<snip>

> I loaded the 2.2.16
> kernel and configured sound as:
> 
>    <M> Sound card support
>    <M> Creative Ensoniq AudioPCI 97 (ES1371)

from a technical POV, ALSA is far superior to the kernel sound
module.
this view is shared by many kernel folks, alan cox among them.
 
> Now the Ensoniq AudioPCI works with standard Linux components,
> including the X Windows mixer.
> 
> Dan

as to "standard", ALSA will be the standard Linux audio architcture
in 2.5
they are currently stabilizing the API and didn't make it into 2.4,
but the decision is made.

just FYI, i'm not intending a holy war against OSS :)

but if you use alsa, you can use all oss programs (with the
emulation code) plus all alsa programs.
with oss, you'll miss a lot of good software.

regards,

jörn

-- 
Jörn Nettingsmeier     
Kurfürstenstr. 49        
45138 Essen, Germany      
http://www.folkwang.uni-essen.de/~nettings/

      reply	other threads:[~2000-07-18 11:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-17 14:32 Ensoniq AudioPCI problem solved Dan Lasley
2000-07-18 11:38 `  [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=marc-linux-sound-96394415130517@msgid-missing \
    --to=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