Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ll-xn!cit-vax!tybalt.caltech.edu!walton
From: walton@tybalt.caltech.edu (Steve Walton)
Newsgroups: comp.sys.amiga
Subject: Re: the 68070 - has it left hyperspace yet?
Message-ID: <2686@cit-vax.Caltech.Edu>
Date: Wed, 13-May-87 15:48:28 EDT
Article-I.D.: cit-vax.2686
Posted: Wed May 13 15:48:28 1987
Date-Received: Sat, 16-May-87 04:22:26 EDT
References: <280@spectrix.UUCP> <110@l5comp.UUCP> <303@rocky.STANFORD.EDU>
Sender: news@cit-vax.Caltech.Edu
Reply-To: walton@tybalt.caltech.edu.UUCP (Steve Walton)
Distribution: world
Organization: Calfornia Institute of Technology
Lines: 21
Keywords: 68070, signetics, Philips, mac/st/amiga UN*X

In article <303@rocky.STANFORD.EDU> ali@rocky.UUCP (Ali Ozer) writes:
>In article <110@l5comp.UUCP> scotty@l5comp.UUCP (Scott Turner) writes:
>> ... The MMU for example would kill most message ports. 
>
>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).

Since none of the Wizards took this up, thought I would.  Nearly EVERY
system call in the Amiga gets a pointer, and thus this pointer would
have to be MEMF_PUBLIC if we had an MMU.  When was the last time
anyone AllocMem'd a NewWindow structure with MEMF_PUBLIC and copied
their window information into it?  I've seen no examples which do.
(Didn't Matt Dillon go through all this at some length a while back?)


    Steve Walton, guest as walton@tybalt.caltech.edu
    AMETEK Computer Research Division, ametek!walton@csvax.caltech.edu
"Long signatures are definitely frowned upon"--USENET posting rules