mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robert Cohen <robert@coorong.anu.edu.au>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>,
	linux-kernel@vger.kernel.org
Subject: Re: Question: Status of VIA chipsets and 2.2 kernels
Date: Thu, 10 May 2001 12:40:06 +1000	[thread overview]
Message-ID: <3AF9FF86.9DB15723@tltsu.anu.edu.au> (raw)
In-Reply-To: <Pine.LNX.4.10.10105091135360.1509-100000@coffee.psychology.mcmaster.ca>

Mark Hahn wrote:
> 
> >  a P3 machine with a ASUS CUV4X-E motherboard which uses the apollo pro
> > 694X northbridge and a 686B southbridge.
> 
> I haven't seen any reports of problem with this; it's the duals that need
> the noapic workaround at the moment.
> 
> > An athlon machine with an ASUS A7V motherboard which uses a KT133
> > (VT8363) northbridge and a 686A southbridge.
> 
> works fine.  my main workstation is a gigabyte version of this,
> and has never had any problems (and delivers great performance).
> 
> > An athlon machine with an ASUS A7V133 motherboard which uses a KT133A
> > (VT8363A) northbridge and a 686B southbridge.
> 
> this is the one that has some kind of issue, for which there are several
> workarounds.  it's not entirely clear whether the workarounds make sense/etc.

I was worried that the P3 machine with the Apollo pro chipset is using
the 686B southbridge and might
share the DMA problems. Anyone know if this is a problem?

--
Robert Cohen
Unix Support
TLTSU
Australian National University
Ph: 612 58389

       reply	other threads:[~2001-05-10  2:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10105091135360.1509-100000@coffee.psychology.mcmaster.ca>
2001-05-10  2:40 ` Robert Cohen [this message]
2001-05-09  7:14 Robert Cohen
2001-05-09 10:23 ` Alan Cox
2001-05-09 15:00 ` Gerhard Mack
2001-05-10  2:54   ` Robert Cohen
2001-05-09 16:22 ` God

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=3AF9FF86.9DB15723@tltsu.anu.edu.au \
    --to=robert@coorong.anu.edu.au \
    --cc=hahn@coffee.psychology.mcmaster.ca \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®