linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: oyhaare@online.no (Øystein Haare)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Via chipset
Date: Wed, 8 Aug 2001 00:36:42 +0100 (BST)	[thread overview]
Message-ID: <E15UGOw-0004H2-00@the-village.bc.nu> (raw)
In-Reply-To: <997225828.10528.4.camel@eagle> from "=?ISO-8859-1?Q?=D8ystein?= Haare" at Aug 08, 2001 01:10:28 AM

> I'm planning on getting a new workstation, and I kinda want an AMD
> system. But it seems that most (all?) motherboards for the amd cpu's us=
> e
> VIA chipsets, and some people have experienced problems with via
> chipsets and linux.

We have seen two big problem sets with the VIA chipsets and Athlon. The
first is a bug in some of the bridges that caused corruption. We had partial
workarounds but as of 2.4.7ac releases (and I sent it to Linus for
2.4.8pre) we have an official workaround based on VIA provided info.

The second problem is that some VIA chipset boards lock up running the
Athlon optimised kernel. This seems to be board specific and we've also had
'setting CAS3 not CAS2' and 'bigger PSU' reports of fixing it for some
people. I'm still trying to put together a detailed enough study of what
is going on to actually take it to VIA and AMD engineers.

So pick a board other folks say work. Personally I am using AMD chipset
boards but I don't think thats actually a required solution to avoid the
problem. 

As to the PIV. Right now I see no reason to go that way. The PIV is going to
need new compiler tools to get good performance at the moment. It also
requires rambus memory. The rambus memory requirement will change soon, the
processor will go down to a smaller die size (0.13u) and should get both
cheaper and cooler. Hopefully intel will also fix the performance problems
with the extra silicon space they will get out of it.

So if you think PIV wait for the new socket, new die size then study reviews
IMHO.

Alan

  parent reply	other threads:[~2001-08-07 23:34 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-07 23:10 Via chipset Øystein Haare
2001-08-07 18:46 ` Bobby D. Bryant
2001-08-07 23:16 ` Dan Hollis
2001-08-07 23:36 ` Alan Cox [this message]
2001-08-07 23:47   ` Larry McVoy
2001-08-08  9:16     ` Janne Pänkälä
2001-08-08 16:09     ` Marco Colombo
2001-08-15  3:25   ` Maxwell Spangler
2001-08-15 11:48     ` Alan Cox
2001-08-15 12:28       ` Bobby D. Bryant
2001-08-15 19:59       ` Dan Hollis
2001-08-15 20:16         ` Alan Cox
2001-08-15 20:27           ` Dan Hollis
2001-08-15 20:32             ` Alan Cox
2001-08-15 21:50               ` Bryan O'Sullivan
2001-08-16 15:35           ` Bob Martin
2001-08-16 21:09             ` Dan Hollis
2001-08-17  3:04               ` Adrian V. Bono
2001-08-20 22:52                 ` Bob Martin
2001-08-08  1:54 ` Ignacio Vazquez-Abrams
2001-08-15 16:46 Ryan C. Bonham
     [not found] <no.id>
2001-08-15 16:09 ` Alan Cox
2001-08-16 16:02 ` Alan Cox
2001-09-12 18:49 VIA chipset Marco Colombo
2001-09-12 19:22 ` Alan Cox
2001-09-12 20:06 ` Jussi Laako
2001-09-12 20:13   ` Marco Colombo
2001-09-12 20:55     ` Anders Peter Fugmann
2001-09-14 17:29     ` Jussi Laako
2001-10-05 10:20 amit yajurvedi
2001-10-15 11:09 grouch
     [not found] <Pine.LNX.4.10.10110151147340.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 19:01 ` grouch
     [not found] <Pine.LNX.4.10.10110151554040.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 20:31 ` grouch
     [not found] <Pine.LNX.4.10.10110151635040.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 21:22 ` grouch
2001-10-17 11:45 grouch

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=E15UGOw-0004H2-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oyhaare@online.no \
    /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;
as well as URLs for NNTP newsgroup(s).