From: Wade Hampton <whampton@staffnet.com>
To: unlisted-recipients:;;@localhost.localdomain (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.2 cs4232 is not SMP safe
Date: Fri, 30 Mar 2001 10:49:46 -0500 [thread overview]
Message-ID: <3AC4AB1A.1D30F40A@staffnet.com> (raw)
In-Reply-To: <20010328200644.C3544@suse.de> <E14iKnd-0006DT-00@the-village.bc.nu> <20010328211050.A21273@suse.de>
Olaf Hering wrote:
>
> On Wed, Mar 28, Alan Cox wrote:
>
> > > But it still jumps into xmon. How can we make that driver SMP safe?
> > > There is no maintainer address in the files.
> >
> > CS4232 has no maintainer. I've had no SMP x86 problems reported with it for
> > a long time but that may be chance
>
> Well, the alsa driver loads but it can not play sound, all you get is a
> strange noise. The same driver (alsa/kernel) works on a UP ppc machine
> (a B50). I will try to get an UP kernel for that machine, it worked once
> around 2.4.3-pre.
I have been using a Dell SMB dual PII/300 box with cs4232 playing my
MP3s
in a loop 24x7 for nearly a year without any glitches. I have tried it
with 2.2 kernels and 2.4.0.
The only problem I have had with the box and sound driver was that I
had to set the PCI quirks flag to 1 (thanks to Alan for pointing me to
it)
to keep it from crashing when playing sound and accessing the floppy
(this got QUITE embarassing when I was doing some custom work for some
high-level folks a while back).
However, I have one beef with the driver. Each time it starts a cut,
I get a loud pop from the speaker. This appears to be a startup
transient and is not present on my other sound card in the box,
a SoundBlaster Vibra 16. This pop happens on ANY play application,
playing ANY file (esdplay, play[sox], vplay, xmms, etc.).
Cheers,
--
Wade Hampton
parent reply other threads:[~2001-03-30 15:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20010328211050.A21273@suse.de>]
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=3AC4AB1A.1D30F40A@staffnet.com \
--to=whampton@staffnet.com \
--cc=linux-kernel@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