Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!hc!lll-winken!uunet!glyph!nichiren
From: nichiren@glyph.UUCP (Andy Heffernan)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Atom / putting hunks in CHIP/FAST memory.  and, 1.4 request
Message-ID: <190@glyph.UUCP>
Date: 3 May 89 04:11:04 GMT
References: <8905012052.AA25549@postgres.Berkeley.EDU> <239@medusa.informatik.uni-erlangen.de>
Reply-To: nichiren@glyph.UUCP (Andy Heffernan)
Organization: Glyph UNIX, Kingston, NY
Lines: 31

In article <239@medusa.informatik.uni-erlangen.de> mlelstv@immd4.informatik.uni-erlangen.de (Michael van Elst ) writes:
		[with respect to special hunk flag bits]
>00 means default memory (MEMF_PUBLIC)

                   No, just 0.

>01 means chip memory (MEMF_CHIP|MEMF_PUBLIC)

                   No, just MEMF_CHIP.

>10 means fast memory (MEMF_FAST|MEMF_PUBLIC)

                   No, just MEMF_FAST.

>11 means another long word follows describing future attributes (not used)

This response provided in case MEMF_PUBLIC ever becomes
semantically meaningful in AllocMem() calls.

$20 will go to Dave Haynie if his MMU-protected AmigaDOS predictions
come to pass.  You've got until December 31st, Dave.

Here's the bill <crinkle, cruckle>.

>
>E-mail: UUCP: ...uunet!unido!fauern!faui45!mlelstv

-- 
-------------------------------------------------------------------------
Andy Heffernan              uunet!glyph!nichiren            [1222 - 1282]
-------------------------------------------------------------------------