Subject: Re: storing nvaliases in NVRAM ('NVRAMRC not valid')
To: Jeff Walther <trag@io.com>
From: Michael <macallan18@earthlink.net>
List: port-macppc
Date: 04/16/2005 10:36:34
--Signature_Sat__16_Apr_2005_10_36_34_-0400_bcglbTO_0d9pdVYZ
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

> The NVRAM is a separate SRAM chip which has an 8KB capacity.  Apple=20
> used several different pin compatible SRAM chips for this=20
> application, from such manufactures as Sony, Samsung and Winbond.=20
> The NVRAMRC file is stored in NVRAM and some other things.
>=20
> So PRAM and NVRAM reside in physically separate chips, and they are=20
> used to store different items, although I don't know which items go=20
> where in any kind of detail.
>=20
> I've tried replacing the 8K chip with a 32KB pin compatible chip, and=20
> the machine works as before, but it still only sees 8KB of NVRAM.  I=20
> guess the address space is built into the firmware or the wireing of=20
> the interface to the NVRAM chip.

Hmm, I remember some UMAX docs saying that one of the differences between t=
he PM9500 and the S900 was that the latter had twice the amount of NVRAM. S=
ince they used vanilla OF 1.0.5 as it came from Apple ( as far as I know th=
ey weren't allowed to mess with it which resulted in some annoying weirdnes=
ses  ) so either there's a way to use more than 8KB or they just got 16KB c=
hips cheaper than 8KB ones.

just my 2c
Michael

--Signature_Sat__16_Apr_2005_10_36_34_-0400_bcglbTO_0d9pdVYZ
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)

iQEVAwUBQmEi+cpnzkX8Yg2nAQKMzgf/UwXbF4+41qYdGL9k/42Buht0oAm3z1+M
Qqwj994YncjjW9gf3sPo7pTUnrUX8uub4+UPc0YGpV/fB5+P4jQgwVx9h2+h21A9
LQ3VBFP0eouDh3On2M5XX9sxmjLPE+gr2eNV0Eagq6SJKXekOSte4E0+W1x82pTi
eD/JIUGHQ0lVqwdjImGv8SedlN84MWD6UfwJX33rQL4iVrjuE/9tsYAePHAo4uRJ
LdKyuqAFPftGk7aW4AkhDE9aucKXp549sIUoOijTCe2mRZAk9TTDfxY4u7XJBP5n
Ixb4Rsj5ss8W4DDlAD8pcSgjmk3mKq5emcrgqAW4lFhq1YbYzy7CIw==
=IR4Y
-----END PGP SIGNATURE-----

--Signature_Sat__16_Apr_2005_10_36_34_-0400_bcglbTO_0d9pdVYZ--