🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.amiga.tech
Article #11721

Re: Introduction to comp.sys.amiga.tech

#11721
From: Kevin Clague
Date: Wed, 08 Mar 1989 15:39
59 lines
2934 bytes
In article <1739@psu-cs.UUCP> bartonr@psu-cs.UUCP (Robert Barton) writes:
>> # 4 : The Amiga's custom graphics and sound chips can only access the
>> first 512K of memory (slow or chip memory). Therefore, anything that
>> these chips use must be in the first 512K of memory. This includes
>> Window, Gadget and BitMap structures that Intuition uses. To make sure
>> that you get chip memory do add the MEMF_CHIP constant to your call to
>> malloc:
>>
>>       foobar *milkchocolate;
>>       milkchocolate = ( foobar * ) AllocMem (sizeof(foobar), MEMF_CHIP);
>>
>> Then copy your data to the memory pointed to by "milkchocolate". 
>>
>> Edwin Hoogerbeets
>> uunet!utai!utcsri!hcr!edwin
>
>  This is a new one to me.  When the OpenWindow() routine allocates the
>memory for the Window structure it asks for MEMF_CLEAR | MEMF_PUBLIC.  Same
>with OpenScreen() when allocating a Screen or RasInfo structure.  Since a
>Screen contains a ViewPort, a RastPort, a BitMap, and a LayerInfo this
>implies that none of these structures need to be in chip memory either.

It is true that things the custom chips need to access need to be in CHIP
RAM.  The "art" or hard part is knowing which things the custom chips
actually access.  Example:

 Bit planes need to be in CHIP RAM, but RastPort and Window structures
do not.  The 680X0 access these higher level structures, and eventually
calls the custom chips to actually manipulate data in your viewport or
screen's bitmaps.

 Here is a list of the places where some of the resources should be
placed (I wish I had RKM's here at work):

  CHIP RAM        NOT CHIP RAM
  ________        ___________
  BitPlanes       BitMap structure
                  RastPort structure
                  LayerInfo structure
                  Window structure
                  NewWindow structure
                  Screen structure
                  NewScreen structure
                  ViewPort structure
  BitPlanes       Image structure
                  Border structure

So you see that really very few things actually need to be in chip RAM.
I hope this helps.

Kevin
-- 
UUCP:  kevin@uts.amdahl.com
  or:  {sun,decwrl,hplabs,pyramid,seismo,oliveb}!amdahl!kevin
DDD:   408-737-5481
USPS:  Amdahl Corp.  M/S 249,  1250 E. Arques Av,  Sunnyvale, CA 94086

[  Any thoughts or opinions which may or may not have been expressed  ]
[  herein are my own.  They are not necessarily those of my employer. ]
Technical Details
Message-ID: <08BrO8cS3A1010LJrFA@amdahl.uts.amdahl.com>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!bbn!apple!oliveb!amdahl!kevin
References: <1739@psu-cs.UUCP>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!bbn!apple!oliveb!amdahl!kevin
From: kevin@uts.amdahl.com (Kevin Clague)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Introduction to comp.sys.amiga.tech
Message-ID: <08BrO8cS3A1010LJrFA@amdahl.uts.amdahl.com>
Date: 8 Mar 89 15:39:16 GMT
References: <1739@psu-cs.UUCP>
Reply-To: kevin@amdahl.uts.amdahl.com (Kevin Clague)
Organization: Amdahl Corporation,  Sunnyvale, CA 94086
Lines: 59