From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Steven Walter <srwalter@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.18 VIA MWQ patch (Athlon stomper) corrupts video wi
Date: Wed, 20 Mar 2002 19:51:28 +0100 [thread overview]
Message-ID: <5D65D3668@vcnet.vc.cvut.cz> (raw)
On 20 Mar 02 at 12:45, Steven Walter wrote:
> I have this problem, as well. The fix for me was simply not to perform
> the fixup at all. I'm not sure if clearing only bit 7 fixes the problem
> on my machine, but would grudgingly try it, if wanted. (I don't have
> particularly ready access to the machine.)
You should find 'Disabling VIA memory write queue: [xx] aa->bb'
in your output. Values 'aa' and 'bb' are important - in other examples
it modifies value from 0x3x to 0x1x. Unfortunately I could not find
any hints whether we should clear bits 6,5 only on VIA_8363_0 if
revision is < 0x80, or whether we should not touch them at all.
In all reports from last september I remember that clearing bit 7 alone
fixed problems, but then patch which clears all three bits appeared
from VIA without real world examples which were affected by it...
Petr Vandrovec
vandrove@vc.cvut.cz
reply other threads:[~2002-03-20 18:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5D65D3668@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=srwalter@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox