From mint-bounce@lists.fishpool.fi  Fri Sep  9 04:25:39 2005
X-Original-To: fnaumann@mail.boerde.de
Delivered-To: fnaumann@mail.boerde.de
Subject: Re: [MiNT] Binutils FIXED!
From: Evan Langlois <Evan@CoolRunningConcepts.com>
To: Mark Duckworth <mduckworth@atari-source.com>
Cc: Petr Stehlik <joy@sophics.cz>, Mint List <mint@fishpool.com>
In-Reply-To: <1126031957.28227.0.camel@mduckworth.phillypark.net>
References: <1126029452.18656.37.camel@mduckworth.phillypark.net>
	 <1126031706.6573.4.camel@joy.home>  <1126031886.6573.6.camel@joy.home>
	 <1126031957.28227.0.camel@mduckworth.phillypark.net>
Content-Type: text/plain; charset=iso-8859-2
Date: Thu, 08 Sep 2005 21:23:17 -0500
Message-Id: <1126232597.14379.28.camel@taro.coolrunningconcepts.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - esc14.midphase.com
X-AntiAbuse: Original Domain - fishpool.com
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - CoolRunningConcepts.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-To: mint-bounce@lists.fishpool.fi
X-original-sender: Evan@CoolRunningConcepts.com
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
X-Virus-Scanned: by amavisd-new at relay.boerde.de
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de
X-Spam-Status: No, hits=0.7 tagged_above=-50.5 required=7.0 tests=AWL,
 BAYES_00, RCVD_IN_SORBS
X-Spam-Level: 
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id j892PdPx006592

On Tue, 2005-09-06 at 14:39 -0400, Mark Duckworth wrote:
> On Tue, 2005-09-06 at 20:38 +0200, Petr Stehlik wrote:
> > Petr Stehlik píše v Út 06. 09. 2005 v 20:35 +0200:
> > > No.
> > > 
> > > fast alloc = do not clear RAM.
> > 
> > LOL, I've been too quick in guessing what do you mean by "fast alloc".
> > Sorry. Konrad's answer is the correct one.
> > 
> > Petr
> 
> Indeed it would seem i've been confused as well.  This seems perfectly
> reasonable that a program may need to run in ST-ram but can alloc
> fastram or vice versa.  Blame the stupid porters (me :( ) ;) 
> 
> Thanks,
> Mark

Your both right.  There are all three.  The old "fastload" flag (bit 0)
is to only clear the BSS and not the whole heap.  Bit 1 allows loading
into FastRAM, Bit 2 allows Malloc from FastRAM, and I think there are
some more bits for memory protection.