public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: doug@lathi.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: cs46xx on ThinkPad A22m and poor quality output
Date: Wed, 27 Feb 2002 10:17:28 -0800	[thread overview]
Message-ID: <3C7D22B8.9070304@us.ibm.com> (raw)
In-Reply-To: <87vgcjvs1p.fsf@localhost.localdomain> <87pu2r1x7s.fsf@localhost.localdomain>

Doug Alcorn wrote:
> I hate to follow up to my own post; however, I managed to get the card
> working well with the alsa cs46xx driver.  This would imply to me that
> it's a bug in the linux kernel driver for the cs46xx (is this referred
> to as the oss driver?).
 >
> BTW, someone suggested I simply turn the volume down using the
> hardware buttons on the keyboard.  The poor sound quality is really
> irrespective of the speaker volume.  Maybe this wasn't clear when I
> talked about the "higher-levels of output".  I'm not sure about the
> right vocabulary.  I guess it's the power output on the individual
> frequency bands.

You aren't crazy.  Lots of us with T2[012]'s have this problem.  It does 
indeed appear to be a problem with the OSS version of the driver. 
Someone had a theory that the APM code stays in an interrupt too long 
and causes the card to get into an unanticipated state, causing the poor 
sound quality.

The weird part is that some of us see the problem often, while some 
never see it at all.  I haven't had it happen in months, so I suspect 
that later versions of the kernel are better equipped to handle it.  At 
least the ALSA one seems to work better.

-- 
Dave Hansen
haveblue@us.ibm.com


  reply	other threads:[~2002-02-27 18:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 21:42 cs46xx on ThinkPad A22m and poor quality output Doug Alcorn
2002-02-27  2:21 ` Doug Alcorn
2002-02-27 18:17   ` Dave Hansen [this message]
2002-03-01  1:29     ` Theodore Tso

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=3C7D22B8.9070304@us.ibm.com \
    --to=haveblue@us.ibm.com \
    --cc=doug@lathi.net \
    --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