From owner-freebsd-hardware Mon May 13 12:02:10 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA13639 for hardware-outgoing; Mon, 13 May 1996 12:02:10 -0700 (PDT) Received: from nol.net (root@dazed.nol.net [206.126.32.101]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA13629 Mon, 13 May 1996 12:02:05 -0700 (PDT) Received: from dazed.nol.net (blh@dazed.nol.net [206.126.32.101]) by nol.net (8.7.5/8.7.3) with SMTP id NAA14409; Mon, 13 May 1996 13:56:32 -0500 (CDT) X-AUTH: NOLNET SENDMAIL AUTH Date: Mon, 13 May 1996 13:56:30 -0500 (CDT) From: "Brett L. Hawn" To: "matthew c. mead" cc: jgreco@brasil.moneng.mei.com, hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Triton chipset with 256k cache caches 32M only? In-Reply-To: <199605131829.OAA02591@neon.Glock.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 13 May 1996, matthew c. mead wrote: > > Assuming that these are Triton-1 chipsets you will find that > > anything over 64m leads to non-caching. I would highly suggest > > getting some of the new ASUS (just my particular favorite) tr-2 > > chipset motherboards, these solve the caching problem along > > with many of the other inherent bugs of tr-1 chipsets. > > Well, I'm positive that anything over 64M will lead to > non-caching. I'm also positive that anything over 32M leads to > non-caching. Any ideas on what I should do to get the upper 8M > (megs 32-39) cached? I'm thinking of purchasing a 512k COAST > module, but I want to make sure that will do it before I buy it. I've not run into the >32mb caching before but I can't say as I ever had >32 && <64 in a machine at any given time. Rather than purchasing the module I'd look into the cost of buying a new tr-2 motherboard w/ 512k pipeline-burst cache (Winbob, the hitatchi cache blows goats). Brett