From mint-bounce@lists.fishpool.fi Mon Nov 15 15:23:14 2004 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <4198BD2F.4070005@utbm.fr> Date: Mon, 15 Nov 2004 15:29:03 +0100 From: Olivier Landemarre User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gerhard Stoll Cc: mint@fishpool.com Subject: Re: [MiNT] Mxalloc() and memory protection References: <200411131122.p41118@b.maus.de> In-Reply-To: <200411131122.p41118@b.maus.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: olivier.landemarre@utbm.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: 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=-1.0 tagged_above=-50.5 required=3.8 tests=BAYES_00 X-Spam-Level: Gerhard Stoll wrote: >PD> (Atari Compendium, TOS.HYP), you'll read that the "bit 3" has a >PD> special meaning > >After I look to some old news I things that this is wrong. What I found is that >for MiNT the bit 3 is defined, but not used (sys/dosmem.c): >-------------------------------cut------------------------------- ># if 0 > /* I'm very suspicious of the 0x08 flag; I can't see how it could > * work as the comment below seems to indicate -- ERS > */ > > /* if the mode argument has the 0x08 bit set then you're trying > * to change the protection mode of a block you already own. > * "size" is really its base address. (new as of 2/6/1992) > */ > if (mode & 0x08) change_prot_status(curproc,size,protmode); ># endif >-------------------------------cut------------------------------- > >I will changed the tos.hyp that bit is reserved. > >Gerhard > > hello Compendium is wrong, here official documentation from Atari comming with Falcon system dev for bit 3: When set, means "change the protection mode of a region to the protection-mode field". You may only do this if you own region; In this case the first argument to Mxalloc is the starting address of the region, as returned from an earlier Mxalloc or Malloc or Pexec (mode 3 and 5) call Olivier