All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Park <opengeometry@yahoo.ca>
To: "Christian Borntr�ger" <linux-kernel@borntraeger.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PC-133 RAM + VIA 686B -> 4 x DIMM or 3 x DIMM ?
Date: Fri, 23 Nov 2001 04:56:58 -0500	[thread overview]
Message-ID: <20011123045658.A3170@node0.opengeometry.ca> (raw)
In-Reply-To: <20011123043303.A3043@node0.opengeometry.ca> <E167CsI-0004Xg-00@mrvdom03.schlund.de>
In-Reply-To: <E167CsI-0004Xg-00@mrvdom03.schlund.de>; from linux-kernel@borntraeger.net on Fri, Nov 23, 2001 at 10:43:20AM +0100

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=euc-kr, Size: 844 bytes --]

On Fri, Nov 23, 2001 at 10:43:20AM +0100, Christian Bornträger wrote:
> > I'm confused by conflicting rumors about VIA 686B chipset:
> >     - some people can get only 3 x DIMM working at PC-133.
> >     - others report that all 4 x DIMM are working at PC-133.
> 
> First of all: 
> This is offtopic for the ___linux kernel___ mailing list.

I tried *.abit, *.asus, *.tyan, *.linux.hardware newsgroups, but got
nowhere.  This was my last resort.

> 
> Nevertheless:
> VIA686B is the southbridge and has no memory controller.
> The VIA694X-northbridge has 6 memory banks.
> 
> if the 3rd and 4th module are single sided its ok. 
> If the 3rd module is double sided you cannot plugin a 4th module.

Thanks!

-- 
William Park, Open Geometry Consulting, <opengeometry@yahoo.ca>.
8 CPU cluster, NAS, (Slackware) Linux, Python, LaTeX, Vim, Mutt, Tin

      reply	other threads:[~2001-11-23  9:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-23  9:33 PC-133 RAM + VIA 686B -> 4 x DIMM or 3 x DIMM ? William Park
2001-11-23  9:43 ` Christian Bornträger
2001-11-23  9:56   ` William Park [this message]

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=20011123045658.A3170@node0.opengeometry.ca \
    --to=opengeometry@yahoo.ca \
    --cc=linux-kernel@borntraeger.net \
    --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 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.