public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Axel Thimm <Axel.Thimm@physik.fu-berlin.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Au-Ja <doelf@au-ja.de>, Yiping Chen <YipingChen@via.com.tw>,
	support@msi.com.tw, info@msi-computer.de, support@via-cyrix.de,
	John R Lenton <john@grulic.org.ar>
Subject: VIA's Southbridge bug: Latest (pseudo-)patch
Date: Sat, 19 May 2001 11:07:21 +0200	[thread overview]
Message-ID: <20010519110721.A1415@pua.nirvana> (raw)

This are the latest suggestions for handling the VIA Southbridge bug as
derived from the hardware site www.au-ja.de (Many thanks to doelf).

Could a linux kernel specialist review and form this pseudo-patch to a real
kernel patch? Given the "old" patch found in 2.4.4 I could have written the
part of setting the PCI registers, but I am totally in the dark as to how to
identify EPOX Mobos and derive their BIOS ID.

Here comes the pseudo-patch:

if( KT133A || KT133 || KX133 ) {
  if( Mainboard=="Epox 8KTA-3(+)" && BIOS>="8kt31417" )
    return 0; /* EPOX already fixed it their way. */
#ifdef NEW_PATCH
  Offset 76: Set bit5=0 and bit4=1 ("every PCI master grand")
#else /* this is already part of 2.4.4 */
  Offset 70: Set bit1=0 ("PCI Delay Transaction = 0")
  Offset 70: Set bit2=0 ("PCI Master Read Caching = 0")
  Offset 75: Set bit0-4 ("0 <=  PCI Latency <= 32")
#endif
}

History (condensed version, more found in [1]):
- When doelf and his colleagues found the Southbridge bug, they already worked
  on a solution, which was adopted by most BIOS updates (but not EPOX) and
  also found its way in 2.4.3-ac7. This patch helped in the majority of the
  buggy boards, but still left some cases unresolved.
- VIA released their own patch ten days ago which tries to solve the Bug
  (viapfd100.exe and the latest 4in1 driver). Not only is this patch only for
  Windows and undocumented, but it also only applies if the running box has a
  Soundblaster card.
- Someone analysed the patch and found the changed PCI settings so that the
  patch could be implemented also for systems without a Soundblaster
  card (see [1]). This is the NEW_PATCH outlined above. This seems to be
  working (all related hardware sites which had discovered the bug are content
  now), so it would be nice to have it in the kernel and test it from within
  linux.

[1] latest english information on the VIA Southbridge bug:
    http://www.au-ja.de/review-kt133a-1-en.html
-- 
Axel.Thimm@physik.fu-berlin.de

             reply	other threads:[~2001-05-19  9:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-19  9:07 Axel Thimm [this message]
2001-05-19 16:11 ` VIA's Southbridge bug: Latest (pseudo-)patch Alan Cox
2001-05-19 20:27   ` VIA politics (was: VIA's Southbridge bug: Latest (pseudo-)patch) Axel Thimm
2001-05-20  0:44   ` VIA's Southbridge bug: Latest (pseudo-)patch Ingo Oeser
2001-05-20 19:40     ` Alan Cox
2001-05-21 17:17       ` Gerhard Mack
2001-05-21 17:25         ` Udo A. Steinberg
2001-05-21 18:21           ` Dan Hollis
2001-05-22  6:11           ` God
2001-05-22  9:10             ` Alan Cox
2001-05-21 18:19         ` Dan Hollis
2001-05-22  6:09         ` God
2001-05-19 16:42 ` Przemyslaw Wegrzyn
2001-06-01 15:18 ` Marc Lehmann
2001-06-01 15:28   ` Jeff Garzik
2001-06-01 20:16     ` Marc Lehmann
2001-06-03 22:10       ` Adrian Cox
2001-06-06 16:24         ` Marc Lehmann
2001-06-06 18:39           ` Dan Hollis
2001-06-06 16:31         ` Gérard Roudier
  -- strict thread matches above, loose matches on Subject: below --
2001-05-21 17:28 Khachaturov, Vassilii

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=20010519110721.A1415@pua.nirvana \
    --to=axel.thimm@physik.fu-berlin.de \
    --cc=YipingChen@via.com.tw \
    --cc=doelf@au-ja.de \
    --cc=info@msi-computer.de \
    --cc=john@grulic.org.ar \
    --cc=linux-kernel@vger.kernel.org \
    --cc=support@msi.com.tw \
    --cc=support@via-cyrix.de \
    /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