Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!mailrus!ncar!boulder!tramp!hunt
From: hunt@tramp.Colorado.EDU (Lee Cameron Hunt)
Newsgroups: comp.sys.amiga.tech
Subject: SetCPU -- why turn CACHE and BURST off?
Keywords: cache, burst, why?
Message-ID: <14956@boulder.Colorado.EDU>
Date: 16 Dec 89 23:53:07 GMT
Sender: news@boulder.Colorado.EDU
Reply-To: hunt@tramp.Colorado.EDU (Lee Cameron Hunt)
Distribution: na
Organization: University of Colorado, Boulder
Lines: 48

I'm the proud owner of a new A2630.  I got mine scavaged from a 2500/30
so I don't have the associated manuals for it yet, so my question may
be answered in there.  But, here goes...

I was looking around my local BBS for programs for 68020/30 machines and
ran across SetCPU (v. 1.5a), Dave Haynie.  I started using the FASTROM option
and that seems to speed things up nicely.  In the SetCPU docs, Dave mentions
that he turns on the instruction cache, off the data cache, and turns off
bursting (NOBURST) for both data and instructions.

My question is: first, why turn off data caching and, second, why exacty
is data and instruction bursting?  (I guess that's actually a two-question
question, oh well...).

I seem to remember vaguely conservations about this utility a while back
(and I didn't pay much attention since I just had a plain 2000).  However,
I *think* I remember the data cache being turned off for fear of DMA       
controllers screwing up somehow (I have a HardFrame 2000).  But, when I
try turning both the CACHE and BURST flags on (for data and inst.) things
seem to work fine.

So, should I worry about having these options enabled?


Also, what does the file "KickFile" do that comes with SetCPU?  And, finally
could anybody give me or tell me how to obtain a CardROMList entry for
a HardFrame 2000?


Thanks ahead of time!  (No more of this "thanks in advance" stuff! :-)
 

--Lee


p.s.  Maybe this is standard practice for SIMMs but I still am a bit agast
by the fact that in order to add the extra 2Mb of on-board 32-bit RAM you
must solder them in. (!)  Why not spend a few more $$s in manufacturing costs
and add sockets?  (I assume there are SIMM sockets). 

Oh, yeah, Dave: when you do figure out how one can add faster 32-bit RAM
(so the board will have fewer or no async. wait states) please let us know.
(I believe you posted saying it involved cutting a trace or something).

One final, final, thing:  I heard thru the graphvine that Amix could be
added to these coprocssor boards.  Where do the ROMs for Amix attach?  On
the memory daughterboard connector?  In one of the already-filled socketed
ROMs on the A2630?  This inquring mind wants to know!