Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!sun-barr!rutgers!cbmvax!drysdale
From: drysdale@cbmvax.commodore.com (Scott Drysdale)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: How does bridgeboard affect memory
Message-ID: <17795@cbmvax.commodore.com>
Date: 18 Jan 91 19:03:43 GMT
References: <11152@darkstar.ucsc.edu> <758@cbmger.UUCP> <759@cbmger.UUCP> <17742@cbmvax.commodore.com> <17745@cbmvax.commodore.com> <765@cbmger.UUCP>
Reply-To: drysdale@cbmvax.commodore.com (Scott Drysdale)
Organization: Commodore, West Chester, PA
Lines: 30

In article <765@cbmger.UUCP> peterk@cbmger.UUCP (Peter Kittel GERMANY) writes:
>In article <17745@cbmvax.commodore.com> drysdale@cbmvax.commodore.com (Scott Drysdale) writes:
>>>>
>>>>Sorry, my program tells only 512 KB for both.
>>>
>>>argh.  what was i thinking?
>>
>>aha!  i was thinking of the addresses that the bridgeboard can reside at.  the
>>bridgeboard can only live on 2 meg address boundaries.
>
>Hmm, is this at all allowed in the autoconfig mechanism? I always
>thought that autoconfig memory space is managed in 64 KB chunks.
>Is then a board allowed to say "No, I don't like the address that
>the system gave me, I WANT a 2 meg boundary!" ???

yes - the autoconfig protocol works in 64k chunks, so any board could locate
itself on a 64K boundary no matter what it's size (i think).  but the
bridgeboard was designed for some reason only to go to 2 meg boundaries.  i
don't know why.

>Best regards, Dr. Peter Kittel  // E-Mail to  \\  Only my personal opinions... 

  --Scotty
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Scott Drysdale           Software Engineer
Commodore Amiga Inc.     UUCP {allegra|burdvax|rutgers|ihnp4}!cbmvax!drysdale
		         PHONE - yes.
"Have you hugged your hog today?"
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=