Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!gatech!hao!ames!oliveb!pyramid!decwrl!labrea!rocky!ali
From: ali@rocky.STANFORD.EDU (Ali Ozer)
Newsgroups: comp.sys.m68k,comp.sys.atari.st,comp.sys.amiga
Subject: Re: the 68070 - has it left hyperspace yet?
Message-ID: <303@rocky.STANFORD.EDU>
Date: Mon, 11-May-87 01:08:06 EDT
Article-I.D.: rocky.303
Posted: Mon May 11 01:08:06 1987
Date-Received: Wed, 13-May-87 01:07:34 EDT
References: <280@spectrix.UUCP> <110@l5comp.UUCP>
Reply-To: ali@rocky.UUCP (Ali Ozer)
Distribution: world
Organization: Stanford University Computer Science Department
Lines: 16
Keywords: 68070, signetics, Philips, mac/st/amiga UN*X
Xref: mnetor comp.sys.m68k:472 comp.sys.atari.st:3372 comp.sys.amiga:4710

In article <110@l5comp.UUCP> scotty@l5comp.UUCP (Scott Turner) writes:
> ... The MMU for example would kill most message ports. If C-A had been
>thinking ahead they would have included an MEMF type for a true "public"
>memory type. If this had been done then message ports could have been 
>allocated using this memory type and on MMU systems this would return a 
>pointer into a shared memory page. ...

But, isn't that what MEMF_PUBLIC is for??? Right now MEMF_PUBLIC doesn't
do a thing, but isn't it supposed to be for the future (the days of the
Amiga 3000, say!) when there's an MMU in the Amiga? I've been a good boy
all this time and have put in MEMF_PUBLIC for all my port, message, and task
memory allocations (so that my programs could work in some future Amiga).
I think an MMU with shared memory pages what C-A had in mind when they
included this flag for memory allocation. 

Ali Ozer, ali@rocky.stanford.edu