All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Calin A. Culianu" <calin@ajvar.org>
To: Martin Eriksson <nitrax@giron.wox.org>
Cc: Petri Kaukasoina <kaukasoi@elektroni.ee.tut.fi>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][highly-experimental] via-mwq (Was: Re: VIA acknowledges North Bridge bug...)
Date: Fri, 7 Dec 2001 13:45:26 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.30.0112071344331.8001-100000@rtlab.med.cornell.edu> (raw)
In-Reply-To: <006d01c17f09$f4d61ab0$0201a8c0@HOMER>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 2238 bytes --]


I wrote a patch as well.. and tested it.. It works fine.  I would
recommend not writing an entirely new function.  It's a bit more efficient
just to overload the athlon bug stomper function and register it for a few
extra chipsets.

I will post my patch tha tbasically works just like your patch but has a
smaller footprint..  :)

-Calin


On Fri, 7
Dec 2001, Martin Eriksson wrote:

> ----- Original Message -----
> From: "Calin A. Culianu" <calin@ajvar.org>
> To: "Petri Kaukasoina" <kaukasoi@elektroni.ee.tut.fi>
> Cc: <linux-kernel@vger.kernel.org>
> Sent: Thursday, December 06, 2001 11:09 PM
> Subject: Re: VIA acknowledges North Bridge bug (AKA Linux Kernel with Athlon
>
> > Here is the webpage:
> >
> > This patch detects the 0305, 3099, 3102, and 3112 (KT133x, KT266x, VT8662,
> > and KLE133) *only*. On these chipsets, it will patch register 55 in the
> > Northbridge, which will supposedly switch off a Memory Write Queue timer.
> > In the KT133A datasheet, register 55 is "reserved". But - yikes! - in the
> > KT266, the documented MWQ register is register 95, not 55. Register 55
> > contains unrelated DDR timing adjustments and could actually be dangerous
> > to program. For this reason, I do not recommend installing this driver on
> > the KT266x chipsets until VIA examines this issue. For now, use WPCREDIT
> > and set bits 5, 6, and 7 to zero in register 95 instead."
> >
> > ----
> >
> > Clearly, we need to modify the via workaround patches to take into account
> > the other via device id's (namely 3099, 3102, and 3112), and for each one
> > change the appropriate register.  Either register 55 or in the case of the
> > kt266x, register 95.  I am grepping through quirks.c right now and it
> > seems this would be the correct file to modify.. any other suggestions on
> > what file to modify?
>
> I've (hastily) put these changes into "arch/i386/kernel/pci-pc.c" and had to
> modify "include/linux/pci_ids.h" too.
>
> The patch is included, but a warning: I have no VIA based computer that I
> can test this on myself...
>
> _____________________________________________________
> |  Martin Eriksson <nitrax@giron.wox.org>
> |  MSc CSE student, department of Computing Science
> |  Umeå University, Sweden
>
>


  parent reply	other threads:[~2001-12-07 18:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-05 19:21 VIA acknowledges North Bridge bug (AKA Linux Kernel with Athlon optimizations bug) Troels Walsted Hansen
2001-12-05 21:09 ` Calin A. Culianu
2001-12-06  0:41   ` VIA acknowledges North Bridge bug (AKA Linux Kernel with Athlon Alan Cox
2001-12-06  8:45     ` Petri Kaukasoina
2001-12-06 22:09       ` Calin A. Culianu
2001-12-07 10:28         ` [PATCH][highly-experimental] via-mwq (Was: Re: VIA acknowledges North Bridge bug...) Martin Eriksson
2001-12-07 12:46           ` Pozsar Balazs
2001-12-07 18:45           ` Calin A. Culianu [this message]
2001-12-06 21:35     ` VIA acknowledges North Bridge bug (AKA Linux Kernel with Athlon Calin A. Culianu

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=Pine.LNX.4.30.0112071344331.8001-100000@rtlab.med.cornell.edu \
    --to=calin@ajvar.org \
    --cc=kaukasoi@elektroni.ee.tut.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nitrax@giron.wox.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.