🚀 go-pugleaf

|With all the talk of the new CoCo's memory management system and the
|discussions wondering why a 68000 was not used I have the following
|thoughts (yes I have ONE now and again :^> )
|
|If memory serves me correct the 68000 can not restart/resume a bus faulted
|instruction.  So regardless of what mkind of MMU you try to hang on it, it
|can not overcome this problem.  As I understand it,  the 68000 does NOT
|ensure the address pointed to on the stack, is the address of the fault
|instruction.  Therefore you can't restart the instruction and 68000 does
|not dump it's micro-state, so you can't resume the faulted instruction.  Is
|this about right?   Motorola you out there?  Guy Harris, this about the
|scheme of things?  Henry of UTZOO, this acurate?

The fact that it is difficult to restart an instruction that received
a bus fault on the 68000 makes it difficult to implement paging.
However, an MMU has other uses besides paging, e.g. to protect processes
from one another, to help utilise memory more efficiently, and
to allow swapping and process duplication (a la fork(1); you can't
implement fork(1), in general, on the 68000 without an MMU).

I consider it a grave mistake not to have included even a rudimentary kind
of address remapping on the Amiga; even just an adder on the address lines
of the 68000 would have simplified the system software and allowed some
kind of swapping to be hacked.

						Thomas.