From: Lee Revell <rlrevell@joe-job.com>
To: Michiel de Boer <x@rebelhomicide.demon.nl>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Chipset addition for the VIA Southbridge workaround / quirk
Date: Wed, 27 Sep 2006 17:44:46 -0400 [thread overview]
Message-ID: <1159393487.1275.52.camel@mindpipe> (raw)
In-Reply-To: <451AE795.6030804@rebelhomicide.demon.nl>
On Wed, 2006-09-27 at 23:05 +0200, Michiel de Boer wrote:
> Also built in is an Creative Labs SB Live! audio device. When i was
> still using windows 98, i experienced corruptions when burning DVD's,
> and after lengthy investigation i discovered i had a buggy
> southbridge.[1]
> Apparently the presence of the SB Live! audio device might even
> accelerate the problem, although it does not actually disappear when
> this PCI card is removed. When i moved to Linux, i decided that
> writing a kernel patch based on the fixup programs i found for windows
> 98 would be appropriate.
Just FYI, the onboard "SBLive" is not a real SBLive! - it uses a newer,
cheaper, and vastly inferior chipset that moves all of the interesting
hardware features of the good old SBLive! into the (Windows) driver.
I would be surprised if it had the same issues as the original emu10k1
chipset, which generated a lot more bus traffic by implementing multiple
stream mixing in hardware.
IOW, this bug is probably unrelated to the SBLive...
Lee
next prev parent reply other threads:[~2006-09-27 21:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 21:05 Michiel de Boer
2006-09-27 21:44 ` Lee Revell [this message]
2006-09-27 22:35 ` Michiel de Boer
2006-09-27 22:59 ` Lee Revell
2006-09-28 0:01 ` Andrew Morton
[not found] <fa.a5JNkmioXw5Nk7TL3per32bVULU@ifi.uio.no>
[not found] ` <fa.26gtk6nrxcQoI9Era+0RigHE+Ug@ifi.uio.no>
2006-09-28 2:11 ` Robert Hancock
2006-09-28 13:51 ` Sergio Monteiro Basto
2006-09-29 16:00 ` Michiel de Boer
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=1159393487.1275.52.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=x@rebelhomicide.demon.nl \
/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
Powered by JetHome