From: Andre Pang <ozone@algorithm.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: Screen corruption in 2.4.18
Date: Mon, 25 Mar 2002 12:43:18 +1100 [thread overview]
Message-ID: <1017020598.420771.13343.nullmailer@bozar.algorithm.com.au> (raw)
In-Reply-To: <200203192112.WAA09721@jagor.srce.hr> <20020323160647.GA22958@hapablap.dyn.dhs.org> <1016953516.189201.5912.nullmailer@bozar.algorithm.com.au> <200203241507.g2OF7WN26069@ls401.hinet.hr>
On Sun, Mar 24, 2002 at 04:07:31PM +0100, Danijel Schiavuzzi wrote:
> > In the meantime, I'd probably suggest a patch which looks for
> > clears only bit 7 of Rx55 if an 8363 and an 8365 is found. I'll
> > whip one up later today.
>
> Yes, should implement some autodetection to detect VT8365 and clear only bit
> 7 and include it in the kernel *as soon as possible* (I don't have any kernel
> programming experience, so don't ask me to do so, although it should be
> something trivial ;))
I've had a quick look at the pci-pc.c file which handles the PCI
fixups, but I can't see of a way to say "if this chip is detected
_and_ that chip is detected, modify this bit in the first chip."
It's possible, but not without some real ugly hackery.
Assuming that _only_ the integrated KT133+KM133 chipset uses the
VT8365 PCI ID (0x8305), it'd be easy to make a special-case patch
for it. My only worry is that other chipsets (like the 'normal'
KT133 without the KM133) use the same PCI ID; we should avoid
modifying the fix for the other chipsets, if possible.
Can somebody with a KT133/KT133A do a "lspci -n" and grep for
'8305'? If it doesn't appear, I'll send off my patch.
--
#ozone/algorithm <ozone@algorithm.com.au> - trust.in.love.to.save
next prev parent reply other threads:[~2002-03-25 1:44 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-19 21:12 Screen corruption in 2.4.18 Danijel Schiavuzzi
2002-03-20 0:03 ` Steven Walter
[not found] ` <200203201506.QAA13795@jagor.srce.hr>
[not found] ` <20020320172516.GA14024@hapablap.dyn.dhs.org>
[not found] ` <200203211209.NAA11121@jagor.srce.hr>
2002-03-21 17:22 ` Steven Walter
[not found] ` <200203222204.XAA01121@jagor.srce.hr>
2002-03-22 23:23 ` Steven Walter
[not found] ` <200203231526.QAA09302@jagor.srce.hr>
2002-03-23 16:06 ` Steven Walter
[not found] ` <200203231741.SAA00071@jagor.srce.hr>
2002-03-23 18:26 ` VIA technical contact [was Screen corruption in 2.4.18] Steven Walter
2002-03-24 7:05 ` Screen corruption in 2.4.18 Andre Pang
2002-03-24 7:16 ` [PATCH] " Steven Walter
[not found] ` <200203241231.g2OCV5X18426@Port.imtp.ilyichevsk.odessa.ua>
2002-03-24 15:59 ` Steven Walter
2002-03-24 16:48 ` Alan Cox
2002-03-24 18:03 ` Steven Walter
2002-03-25 2:01 ` Andre Pang
2002-03-24 15:07 ` Danijel Schiavuzzi
2002-03-24 16:51 ` Alan Cox
2002-03-24 17:13 ` Danijel Schiavuzzi
2002-03-25 1:43 ` Andre Pang [this message]
2002-03-25 2:40 ` Steven Walter
2002-03-25 3:00 ` Andre Pang
2002-03-25 8:50 ` Marc Wilson
2002-03-25 17:07 ` Daniel Gryniewicz
2002-03-25 21:02 ` Steven Walter
2002-03-25 21:19 ` Marc Wilson
2002-03-29 2:06 ` Andre Pang
2002-03-29 3:16 ` Marc Wilson
2002-03-25 1:55 ` Andre Pang
2002-03-25 19:52 ` Danijel Schiavuzzi
-- strict thread matches above, loose matches on Subject: below --
2002-03-25 17:59 Petr Vandrovec
2002-03-28 22:46 Bill Hammock
2002-03-29 0:14 ` Danijel Schiavuzzi
2002-03-29 2:05 ` Andre Pang
2002-03-29 12:26 Petr Vandrovec
2002-04-02 21:43 Chris Rankin
2002-04-02 22:33 ` Richard B. Johnson
2002-04-02 22:40 ` Chris Rankin
2002-04-03 14:00 ` Richard B. Johnson
2002-04-03 20:34 ` Chris Rankin
2002-04-02 23:38 ` Erik Ljungström
2002-04-02 22:50 Petr Vandrovec
2002-04-02 22:09 ` Chris Rankin
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=1017020598.420771.13343.nullmailer@bozar.algorithm.com.au \
--to=ozone@algorithm.com.au \
--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