Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!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: Atom / putting hunks in CHIP/FAST memory.  and, 1.4 request
Message-ID: <239@medusa.informatik.uni-erlangen.de>
Date: 2 May 89 08:43:43 GMT
References: <8905012052.AA25549@postgres.Berkeley.EDU>
Organization: IMMD IV, University of Erlangen, W-Germany
Lines: 25

dillon@POSTGRES.BERKELEY.EDU (Matt Dillon) writes:


>	Out of curiosity I fooled around a bit with Atom to see where in
>HUNKS object/executable format it set the bits.  It sticks the bits in the
>type field of the hunk.  i.e. HUNK_HEADER and other types use up only the
>lower word, leaving 16 flag bits free.

As I know (i.e. my AmigaDos Technical Manual), there are two bits 
that determine the memory type of a HUNK. They are the two MSB's
in the size field of a hunk.
Since hunk size is counted in term of long words these bits
will never be used, even in 32bit address space.

00 means default memory (MEMF_PUBLIC)
01 means chip memory (MEMF_CHIP|MEMF_PUBLIC)
10 means fast memory (MEMF_FAST|MEMF_PUBLIC)
11 means another long word follows describing future attributes (not used)
(Maybe you have to exchange the 01 with the 10 definition)

Of course, the magics for hunk types fit in 16 bits but are defined as LONG.

				Michael van Elst

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