Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!hc!lll-winken!uunet!mcvax!unido!fauern!immd4.informatik.uni-erlangen.de!mlelstv
From: mlelstv@immd4.informatik.uni-erlangen.de (Michael van Elst )
Newsgroups: comp.sys.amiga.tech
Subject: Re^2: Atom / putting hunks in CHIP/FAST memory.  and, 1.4 request
Message-ID: <247@medusa.informatik.uni-erlangen.de>
Date: 5 May 89 11:34:28 GMT
References: <8905012052.AA25549@postgres.Berkeley.EDU> <239@medusa.informatik.uni-erlangen.de> <190@glyph.UUCP>
Organization: IMMD IV, University of Erlangen, W-Germany
Lines: 15

nichiren@glyph.UUCP (Andy Heffernan) writes:
>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.
> ...
That's right Andy. There is no need for MEMF_PUBLIC and it would break
MEMF_PUBLIC rules if someone implements a protected AmigaDOS.

The only thing that I want to point on is, that memory type information
isn't placed in the hunk type fields BUT in the hunk size field.

				Michael van Elst

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