mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicholas Knight <nknight@pocketinet.com>
To: linux-kernel@vger.kernel.org
Subject: Who fixed via82cxxx_audio.c ?
Date: Tue, 25 Dec 2001 03:20:02 -0800	[thread overview]
Message-ID: <WHITExvWvqzAoa2JB1n000005b3@white.pocketinet.com> (raw)

Several months back, I started trying to get the via82cxxx_audio.c 
sound driver fixed, it was causing lockup problems whenever something 
opened and/or used the mixer. A similar route was taken as I took with 
the Athlon optimization problems, trying to get everyone to send as 
much information as possible on their cards using this driver. This 
never really led anywhere, and the only information gleaned was that 
dropping buffers down to extremely low levels helped in some cases, but 
not all, and didn't always completely fix it.

After 2.4.10 was released, I stopped updating my kernel for a variety 
of reasons (less time spent in linux, long story.) However a while back 
I updated to 2.4.16, and decided to load XMMS just for the hell of it, 
not 5 minutes ago. To my delight, the problem is completely solved. I 
checked all the changelogs from 2.4.10 to now, and the only mention I 
found searching for "97" (ac97 codec is used) and "via82" was in the 
2.4.*17* changelog, saying Jeff was no longer the maintainer.
I'd like to know who managed to find and fix the underlying cause, so I 
can both thank them, and find out what the heck this problem that 
plagued me for many months was.

             reply	other threads:[~2001-12-25 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-25 11:20 Nicholas Knight [this message]
2001-12-25 16:16 ` Peter Wächtler
2001-12-27 15:53   ` Jeff
2002-01-03  3:24     ` Itai Nahshon

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=WHITExvWvqzAoa2JB1n000005b3@white.pocketinet.com \
    --to=nknight@pocketinet.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

all inboxes | Powered by JetHome®