All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Kristofer T. Karas" <ktk@bigfoot.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [ALSA BUG] VIA 82xx broken by 0.9.0rc7 patch
Date: Tue, 25 Mar 2003 12:58:49 +0100	[thread overview]
Message-ID: <s5hel4vpshy.wl@alsa2.suse.de> (raw)
In-Reply-To: <1048520403.18362.31.camel@pinhead>

[-- Attachment #1: Type: text/plain, Size: 1776 bytes --]

At 24 Mar 2003 10:40:03 -0500,
Kristofer T. Karas <ktk@bigfoot.com> wrote:
> 
> Hello Takashi,
> 
> I upgrade my via-82xx driver from 0.9.0rc6 to 0.9.2 and found that the
> sound quality patch (applied somewhere in the 0.9.0rc1 timeframe) seemed
> to have been lost/reverted.  Working backwards to find the point at
> which things broke, it appears to be your kernel driver patch made in
> mid December (between 0.9.0rc6 and 0.9.0rc7).  I browsed alsa-devel and
> alsa-users to see if this had been reported previously, but I have seen
> little other than random bug-reports on alsa-user (most recently one
> about "Noise").
> 
> Although the 8233 driver "functioned" throughout most of 0.9.0beta...,
> sound quality was dreadful.  The output seemed to be a combination of
> being clipped and passed through a flanger.  The beat frequency of the
> "flanger" effect could be reduced to tolerable levels if the input
> sampling frequency was set to 48KHz rather than 44.1 or whatever.
> 
> Then, sometime in the 0.9.0rc1 timeframe (sorry, I don't remember just
> which version) a patch to 8233 fixed the problem.  That is, until
> 0.9.0rc7.
> 
> Since you're the submitter of the patch in question, I thought I'd send
> this report your way...

could you try the attached patch?  it might solve the problem if you
mentioned about OSS applications.

except for such a hidden bug, the difference between 0.9.0rc6 and rc7
is the use of the DSX channels as the first pcm device.  if the above
patch doesn't fix, please try to use hw:0,1 (for alsa native) or
/dev/adsp (for oss) as the sound device.

if the second pcm device works, then your chip model doesn't support
DSX channels well.  maybe it's better to put the module option to
specify the chip model explicitly...


Takashi

[-- Attachment #2: via-0.9.2-fix.dif --]
[-- Type: application/octet-stream, Size: 648 bytes --]

Index: alsa-kernel/pci/via82xx.c
===================================================================
RCS file: /suse/tiwai/cvs/alsa/alsa-kernel/pci/via82xx.c,v
retrieving revision 1.38
diff -u -r1.38 via82xx.c
--- alsa-kernel/pci/via82xx.c	3 Mar 2003 16:56:44 -0000	1.38
+++ alsa-kernel/pci/via82xx.c	25 Mar 2003 11:57:59 -0000
@@ -843,12 +843,11 @@
 	int changed = 0;
 
 	spin_lock(&rec->lock);
-	if (rec->rate) {
-		if (rec->rate != rate && rec->used > 1) {
+	if (rec->rate != rate) {
+		if (rec->rate && rec->used > 1) { /* already set */
 			spin_unlock(&rec->lock);
 			return -EINVAL;
 		}
-	} else {
 		rec->rate = rate;
 		changed = 1;
 	}

       reply	other threads:[~2003-03-25 11:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1048520403.18362.31.camel@pinhead>
2003-03-25 11:58 ` Takashi Iwai [this message]
     [not found]   ` <1048713467.12394.29.camel@pinhead>
2003-03-27 11:04     ` [ALSA BUG] VIA 82xx broken by 0.9.0rc7 patch Takashi Iwai

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=s5hel4vpshy.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=ktk@bigfoot.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.