From: Thorsten Kranzkowski <dl8bcu@dl8bcu.de>
To: linux-alpha@vger.kernel.org, Ryan Kirkpatrick <linux@rkirkpat.net>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Subject: Re: XLT366 Memory Compatiblity...
Date: Tue, 8 Jun 2004 19:32:37 +0000 [thread overview]
Message-ID: <20040608193237.A31694@Marvin.DL8BCU.ampr.org> (raw)
In-Reply-To: <20040608180335.GJ20632@lug-owl.de>; from jbglaw@lug-owl.de on Tue, Jun 08, 2004 at 08:03:35PM +0200
On Tue, Jun 08, 2004 at 08:03:35PM +0200, Jan-Benedict Glaw wrote:
> On Tue, 2004-06-08 17:56:12 +0000, Thorsten Kranzkowski <dl8bcu@dl8bcu.de>
> wrote in message <20040608175612.B31492@Marvin.DL8BCU.ampr.org>:
> > On Tue, Jun 08, 2004 at 02:52:50PM +0200, Jan-Benedict Glaw wrote:
> > > On Tue, 2004-06-08 05:46:54 -0600, Ryan Kirkpatrick <linux@rkirkpat.net>
> > > wrote in message <Pine.LNX.4.21.0406080536550.13212-100000@magellan.rkirkpat.net>:
> > > > utilized they work fine. When fully utilized, they just don't work.
> > >
> > > As I said, parity != ECC.
> >
> > well he said 36 chips which equals 4 bit ECC per 32 bit word.
>
> Or one bit per byte... *digging up some RAM* Ah, these do have 10 or 20
> chips, so that's 2 bits per byte (which I expected).
Quoting from my DS20 manual (DP264 actually):
"The 72-bit, 100 MHz DIMMs consist of 64 Bits of data and 8 bits of ECC, ..."
These are 200 pin sticks which are definitely not found in PC World :)
I assume Ryans memory is bog-standard 72Pin-PS/2 (currently googling to
find a proof) and also with that it's definitely 4bits/32bit. Quoting
from ref_memory.txt that describes my noname-board:
Table 3-1 Possible Memory Capacities
Organization SIMM Bank BCR<SBE> BCR<RAS> BMR
size size
----------------------------------------------------------------
1 Mbit x 36 4 Mbyte 8 Mbyte 0 0011b 0070.0000
2 Mbit x 36 8 Mbyte 16 Mbyte 1 0011b 00F0.0000
[...]
Unfortunately most useful Alpha docs seem to be gone by today - the
closest I could find is:
http://hvdkooij.xs4all.nl/docs/RedHatLinuxAlpha/machinexlt.html
which also suggests 36 Bit RAM.
Now I'm curious what kind of RAM-Sticks _you_ found in your black-box?
are all (10,20) chips of the same size and type? Any stickers that
suggest a clue?
> Melle? Not all that far away:) I'm from Hörste (near Halle/Westf.).
Ein freundliches Hallo nach Nordrhein Westfahlen! ;-)
> MfG, JBG
Bis denn,
Thorsten
--
| Thorsten Kranzkowski Internet: dl8bcu@dl8bcu.de |
| Mobile: ++49 170 1876134 Snail: Kiebitzstr. 14, 49324 Melle, Germany |
| Ampr: dl8bcu@db0lj.#rpl.deu.eu, dl8bcu@marvin.dl8bcu.ampr.org [44.130.8.19] |
-
To unsubscribe from this list: send the line "unsubscribe linux-alpha" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-06-08 19:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 11:46 XLT366 Memory Compatiblity Ryan Kirkpatrick
2004-06-08 12:52 ` Jan-Benedict Glaw
2004-06-08 17:56 ` Thorsten Kranzkowski
2004-06-08 18:03 ` Jan-Benedict Glaw
2004-06-08 19:32 ` Thorsten Kranzkowski [this message]
2004-06-08 20:26 ` Jan-Benedict Glaw
2004-06-09 0:29 ` Thorsten Kranzkowski
2004-06-09 11:28 ` Ryan Kirkpatrick
2004-06-14 11:55 ` Ryan Kirkpatrick
2004-06-14 21:04 ` Thorsten Kranzkowski
2004-06-16 12:40 ` Ryan Kirkpatrick
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=20040608193237.A31694@Marvin.DL8BCU.ampr.org \
--to=dl8bcu@dl8bcu.de \
--cc=jbglaw@lug-owl.de \
--cc=linux-alpha@vger.kernel.org \
--cc=linux@rkirkpat.net \
/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