Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!mailrus!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Chip RAM
Message-ID: <60278@sun.uucp>
Date: 18 Jul 88 18:08:22 GMT
References: <3150@polya.Stanford.EDU> <6428@well.UUCP> <2242@sugar.UUCP> <735@applix.UUCP> <11717@agate.BERKELEY.EDU> <2327@antique.UUCP> <737@applix.UUCP> <2333@antique.UUCP> <4790@killer.UUCP>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 21

In article <4790@killer.UUCP> ltf@killer.UUCP (Lance Franklin) writes:
> ...just out of curiosity, does LoadSeg ever span CHIP and FAST ram when 
> loading hunks? 

No, LoadSeg() can't know if there are internal relative references in the
chunk so it has to treat a chunk as an atomic unit. All languages for the
Amiga will not split data declarations across chunks.

> ...with the possibility, in the future, of machines with 1 meg of CHIP 
> ram, where do I go to find out the actual end of CHIP ram on any given 
> machine.

The beauty of this system is that this information is never needed. If 
you need to know how much chip RAM is available at a given time you can
call AvailMem(MEMF_CHIP) and if you want to know the biggest chunk of it
available you can call AvailMem(MEMF_CHIP+MEMF_LARGEST). Note that on 
future machines there is no restriction that Chip ram even start at 0!

--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.