Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!usc!samsung!uakari.primate.wisc.edu!ames!amdahl!pacbell!hoptoad!peora!tarpit!bilver!alex
From: alex@bilver.UUCP (Alex Matulich)
Newsgroups: comp.sys.amiga
Subject: Re: Memory protection for all amiga's
Message-ID: <532@bilver.UUCP>
Date: 17 Mar 90 03:28:51 GMT
References: <227.25ff6050@waikato.ac.nz>
Reply-To: alex@bilver.UUCP (Alex Matulich)
Organization: W. J. Vermillion, Winter Park, FL
Lines: 18

In article <227.25ff6050@waikato.ac.nz> hamish@waikato.ac.nz writes:
>Putting an MMU into the amiga requires the addition of just one chip, the
>68451 MMU. This is the 24/16 bit version of the 68851, and is designed to

The problem with that is that you could no longer multitask well. 
Communication between processes on the Amiga is accomplished by one process
passing a message pointer to another process.  Only a pointer is passed,
not the entire message.  This means that the tasks in question must share
the same address space.  An MMU would prohibit that.  An MMU causes each
process to run in its own "aritifically-induced" address space, so a pointer
from one process will not point to the same address as the same value of
that pointer for another process.

-- 
     ///  Alex Matulich
    ///  Unicorn Research Corp, 4621 N Landmark Dr, Orlando, FL 32817
\\\///  alex@bilver.UUCP    ...uunet!tarpit!bilver!alex
 \XX/  From BitNet use: bilver!alex@uunet.uu.net