Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cbmvax!cbmehq!babylon!rbabel
From: rbabel@babylon.rmt.sub.org (Ralph Babel)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: GVP Series II + RAM and A2630 memory
Message-ID: <08521.AA08521@babylon.rmt.sub.org>
Date: 15 Jun 91 18:30:40 GMT
References: <1991Jun16.023027.8382@actrix.gen.nz>
Reply-To: cbmvax.commodore.com!cbmehq!babylon!rbabel (Ralph Babel)
Lines: 53

In article <1991Jun16.023027.8382@actrix.gen.nz>,
keith@actrix.gen.nz (Keith Stewart) writes:

> Using my GVP Info programme I see that I have 2 meg at
> 200000 - 3FFFFF and 4 meg at 600000-9ffffff.

Since 4-meg PICs may also be placed at 4-meg boundaries,
this is certainly a deficiency of the expansion.library's
AllocBoardMem() implementation under 1.3.

> I suppose the A2360 2 meg is at 200000 and the GVP mem is
> at 600000

Yes. GVPInfo's "boards" option should tell you.

> If I put an extra 2 meg on the A2360 then will my 32bit
> mem go from 200000 to 5FFFFF and then my GVP mem will
> still go from 600000 - 9fffff

Yes.

> Will I be able to merge this mem

Yes, using MergeMem.

> or will it be automatically merged through the magic of
> autoconfig.

Prior to 2.0: no.

> If i leave just 2 meg on the A2360 can I make it config
> behind the GVP mem

No, unless you want to patch expansion.library.

> What is the optimum mix of GVP mem ( it goes up in two meg
> lots and can have 6 meg on the board) and A2360 mem for:
                    ^^^^^
Without the 2630, it's really 8 megs, of course.

> (1) Contiguous memory
>
> (2) speedy memory

Probably 4 megs each plus MergeMem, unless an application
allocates memory from the end of the free-memory pool.

> It looks like the A2360 will be purchased as the GVP
> distributors seem unable

Hm, something's missing here. :-)

Ralph