Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: A3000 DATA Cache (Can we PLEASE Settle this?)
Message-ID: <22514@cbmvax.commodore.com>
Date: 17 Jun 91 20:45:52 GMT
References: <1991May26.091925.20814@news.iastate.edu> <21999@cbmvax.commodore.com> <274.2857ae21@intersil.uucp> <22458@cbmvax.commodore.com> <276.285b897c@intersil.uucp> <22494@cbmvax.commodore.com>
Reply-To: daveh@cbmvax.commodore.com (Dave Haynie)
Distribution: na
Organization: Commodore, West Chester, PA
Lines: 17

In article <22494@cbmvax.commodore.com> mks@cbmvax.commodore.com (Michael Sinz) writes:

>Also, if you do not have SCRAM, it may be a bad idea to burst at all since
>a burst transfer is just as slow as a normal transfer.

No.  The 68030's burst bit is global, and applies to the entire system.  Just
because on-board memory doesn't burst is no reason to disable it.  Setting that
bit simply means that the 68030 will request burts when it's capable of running
them.  Memory systems, on-board, coprocessor, and Zorro III, which are capable
of bursting are responsible for acknowledging the burst, independently of any
request.  If, in any cycle, both a request and an acknowledge take place, a
real burst cycle will proceed.

-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
	"This is my mistake.  Let me make it good." -R.E.M.