Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!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^3: Atom / putting hunks in CHIP/FAST memory. and, 1.4 req
Message-ID: <262@medusa.informatik.uni-erlangen.de>
Date: 17 May 89 14:03:50 GMT
References: <238@mindlink.UUCP>
Organization: IMMD IV, University of Erlangen, W-Germany
Lines: 17

a218@mindlink.UUCP (Charlie Gibbs) writes:

>     Conclusion: The MEMF_CHIP and MEMF_FAST bits are set in the hunk
>type field in object modules.  In load modules, MEMF_CHIP and MEMF_FAST
>are set both in the hunk type fields and the hunk length fields in the
>hunk_header table.  Under no circumstances are MEMF_CHIP and MEMF_FAST
>set in the length field at the beginning of a hunk itself.

Thanks for testing this. I've never looked at these bits but trusted the
manual since it points out why the length bits were chosen and why they
doesn't harm even in 32bit address space.
Nevertheless, the hunk length fields in the hunk_header table are necessary
for the loader since it allocates all the memory before actually loading
the hunks.
				Michael van Elst

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