Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think.com!linus!linus!eachus
From: eachus@linus.mitre.org (Robert I. Eachus)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Dhrystones 2.1
Message-ID: <EACHUS.90Nov15140452@aries.linus.mitre.org>
Date: 15 Nov 90 19:04:52 GMT
References: <1990Nov11.093823.8369@cunixf.cc.columbia.edu>
Sender: usenet@linus.mitre.org
Organization: The Mitre Corporation, Bedford, MA
Lines: 17
In-reply-to: es1@cunixb.cc.columbia.edu's message of 11 Nov 90 09:38:23 GMT


     Are you using SetCPU to turn on the data cache in the 68030?  (I
don't think you need to use FASTROM.)  This sounds about like the
right difference.  (Under 1.3 the data cache is off by default, since
with some DMA controllers it could cause problems, but I think I
remember reading that the 3000s disk controller and hddisk.device do
the "right" things.  (I have a 2090 and a 2630 card and I have never
had a problem caused by the data cache. SetCPU leaves both data and
instruction caching off for the CHIP memory. -- Thanks Dave :-)

--

					Robert I. Eachus

with STANDARD_DISCLAIMER;
use  STANDARD_DISCLAIMER;
function MESSAGE (TEXT: in CLEVER_IDEAS) return BETTER_IDEAS is...