Path: utzoo!utgpu!water!watmath!clyde!rutgers!ucla-cs!zen!ucbcad!pasteur!ucbvax!hoser.berkeley.edu!bryce
From: bryce@hoser.berkeley.edu (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Re: Hurricane 68020 & O/S speedup
Keywords: 68020 AmigaDOS ROM
Message-ID: <22578@ucbvax.BERKELEY.EDU>
Date: 14 Jan 88 18:01:22 GMT
References: <271@dalcsug.UUCP> <4989@well.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: bryce@hoser.berkeley.edu (Bryce Nesbitt)
Organization: The Logic Foundation
Lines: 34

In article <4989@well.UUCP> ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab) writes:
>In article <271@dalcsug.UUCP> peter@dalcsug.UUCP (R. Andrew MacRae) writes:
>
>	I just sent a letter to Dale asking why ExecBase isn't moved into
>Autoconfig RAM after boot up.  He said most of the system is operational by
>the time Exec gets around to Autoconfiging stuff, and thus ExecBase is too
>difficult to move by that time.

HA!  Hate to contradict Mr. Luck, but I've hacked that area of the rom
into submission.  The bugs in that section kept taking out my recoverable
ram disk.  This is now fixed; and I don't read from any write-only chip
registers.

Both execbase and THE SUPERVISOR STACK end up in chip on a non-$C00000
machine.  Regardless, I'm confident that they could be moved to normal
autoconfig memory with manageable hassle.

Since I don't have "normal autoconfig" memory, I have no 
compelling reason to do this.  I am available for rent, however. :-)


>	The point of this is that, if ExecBase is hard to move, the whole of
>KickStart is probably next to impossible. 

Nah, you do it in hardware.  Just set your 32bit memory to respond to
the proper address range.


	Wait!  Sniff the air?  Am I just blowing smoke?  Hope not!

|\ /|  . Ack! (NAK, SOH, EOT)
{o O} . bryce@hoser.berkeley.EDU -or- ucbvax!hoser!bryce (or try "cogsci")
 (")
  U	"Your theory is crazy... but not crazy enought to be true." -Niels Bohr