From: "John W. Linville" <linville@tuxdriver.com>
To: Greg Stark <gsstark@MIT.EDU>
Cc: Andrew Morton <akpm@osdl.org>,
s0348365@sms.ed.ac.uk, linux-kernel@vger.kernel.org,
pmcfarland@downeast.net
Subject: Re: OSS Audio borked between 2.6.6 and 2.6.10
Date: Mon, 14 Mar 2005 10:33:25 -0500 [thread overview]
Message-ID: <20050314153323.GA7801@tuxdriver.com> (raw)
In-Reply-To: <87u0nevc11.fsf@stark.xeocode.com>
On Mon, Mar 14, 2005 at 03:59:06AM -0500, Greg Stark wrote:
> Well, I built a slew of kernels but found it on the first reboot.
>
> 2.6.7 doesn't work.
> > 2.6.7:
> > [sound/oss] remove bogus CIV_TO_LVI
> >
> > This patch removes a pair of bogus LVI assignments. The explanation in
> > the comment is wrong because the value of PCIB tells the hardware that
> > the DMA buffer can be processed even if LVI == CIV.
> >
> > Setting LVI to CIV + 1 causes overruns when with short writes
> > (something that vmware is very fond of).
Pretty sure this is/was the problem. I found this to be causing
a problem with Wolfenstein: Enemy Territory. The patch to reverse
this change appears to have been merged into 2.6.11. I suggest you
try that one. :-)
Good luck!
John
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2005-03-14 15:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 18:31 OSS Audio borked between 2.6.6 and 2.6.10 Greg Stark
2005-03-13 6:52 ` Patrick McFarland
2005-03-13 22:26 ` Greg Stark
2005-03-14 0:48 ` Martin Schlemmer
2005-03-14 1:03 ` Alistair John Strachan
2005-03-14 3:50 ` Greg Stark
2005-03-14 4:07 ` Andrew Morton
2005-03-14 4:42 ` Greg Stark
2005-03-14 4:55 ` Andrew Morton
2005-03-14 5:39 ` Greg Stark
2005-03-14 5:57 ` Andrew Morton
2005-03-14 6:21 ` Greg Stark
2005-03-14 6:48 ` Andrew Morton
2005-03-14 8:59 ` Greg Stark
2005-03-14 9:53 ` Andrew Morton
2005-03-14 15:40 ` Greg Stark
2005-03-14 15:52 ` John W. Linville
2005-03-22 0:38 ` Andrew Morton
2005-03-22 4:16 ` Greg Stark
2005-03-14 15:33 ` John W. Linville [this message]
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=20050314153323.GA7801@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akpm@osdl.org \
--cc=gsstark@MIT.EDU \
--cc=linux-kernel@vger.kernel.org \
--cc=pmcfarland@downeast.net \
--cc=s0348365@sms.ed.ac.uk \
/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