From: Andre Pang <ozone@algorithm.com.au>
To: Steven Walter <srwalter@yahoo.com>,
alan@lxorguk.ukuu.org.uk, davej@suse.de, torvalds@transmeta.com,
marcelo@conective.com.br, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: Screen corruption in 2.4.18
Date: Mon, 25 Mar 2002 13:01:13 +1100 [thread overview]
Message-ID: <1017021673.923717.13530.nullmailer@bozar.algorithm.com.au> (raw)
In-Reply-To: <200203192112.WAA09721@jagor.srce.hr> <1016953516.189201.5912.nullmailer@bozar.algorithm.com.au> <20020324071604.GA15618@hapablap.dyn.dhs.org> <200203241231.g2OCV5X18426@Port.imtp.ilyichevsk.odessa.ua> <20020324155930.GA20926@hapablap.dyn.dhs.org>
On Sun, Mar 24, 2002 at 09:59:30AM -0600, Steven Walter wrote:
> Here is a patch which should apply cleanly to everyone's tree, which
> only clears bit 7 on all chips except the KT266. No problems have been
> reported there, so I'm leaving well enough alone. Please apply.
I don't think the patch should be that generic; we're into dragon
territory here already. We should follow VIA's fix by default
(clear bits 5, 6, 7), and clear bit 7 only if a VT8365 is
detected.
Even then, I personally want to do some checking to see that the
VT8365 is the real culprit, before firing off a patch which could
affect all other VIA users. I don't want hate mail coming into
my inbox 8).
--
#ozone/algorithm <ozone@algorithm.com.au> - trust.in.love.to.save
next prev parent reply other threads:[~2002-03-25 2:02 UTC|newest]
Thread overview: 26+ 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 [this message]
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
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
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=1017021673.923717.13530.nullmailer@bozar.algorithm.com.au \
--to=ozone@algorithm.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conective.com.br \
--cc=srwalter@yahoo.com \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.