All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: ozone@algorithm.com.au (Andre Pang)
Cc: srwalter@yahoo.com (Steven Walter),
	dschiavu@public.srce.hr (Danijel Schiavuzzi),
	BrehmTomB@aol.com (Tom Brehm), teastep@shorewall.net (Tom Eastep),
	xcp@whisper.jaggnet.org (Bill Hammock),
	bds@jhb.ucs.co.za (Berend De Schouwer),
	vda@port.imtp.ilyichevsk.odessa.ua (Denis Vlasenko),
	VANDROVE@vc.cvut.cz (Petr Vandrovec),
	linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Summary of KL133/KM133 problems w/2.4.18 (screen corruption/MWQ)
Date: Mon, 1 Apr 2002 11:19:11 +0100 (BST)	[thread overview]
Message-ID: <E16ryu7-00083Z-00@the-village.bc.nu> (raw)
In-Reply-To: <1017644966.218140.3006.nullmailer@bozar.algorithm.com.au> from "Andre Pang" at Apr 01, 2002 05:09:26 PM

> Note that this is exactly what the VIA patches for Windows do:
> the VIA 4in1 drivers normally clear bits 5, 6 and 7 of register
> 55, but they do not clear bit 5 if the motherboard is a K[LM]133.
> This occurs on Windows 98 and Windows XP, and indicates to me
> that what this patch does should be the correct behaviour.

Thanks for doing the research

> If all goes well, I'll submit it to Alan/Marcelo/Dave.

I'll throw it into the -ac tree anyway and get you some coverage testing

  reply	other threads:[~2002-04-01 10:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-01  7:09 [RFC][PATCH] Summary of KL133/KM133 problems w/2.4.18 (screen corruption/MWQ) Andre Pang
2002-04-01 10:19 ` Alan Cox [this message]
2002-04-02  4:52 ` Tom Eastep

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=E16ryu7-00083Z-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=BrehmTomB@aol.com \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=bds@jhb.ucs.co.za \
    --cc=dschiavu@public.srce.hr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ozone@algorithm.com.au \
    --cc=srwalter@yahoo.com \
    --cc=teastep@shorewall.net \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=xcp@whisper.jaggnet.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 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.