From mint-bounce@lists.fishpool.fi Thu Nov 11 00:27:24 2004 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: mint@lists.fishpool.fi From: =?ISO-8859-1?Q?Philipp_Donz=E9?= Subject: [MiNT] Mxalloc() and memory protection Date: Thu, 11 Nov 2004 00:25:35 +0100 X-Mailer: Apple Mail (2.619) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: philipp.donze@epfl.ch 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: Hi, While solving a problem with memory protection, I "googled" the internet for documentation on Mxalloc(). In the past (and in a test application which I run under MiNT 1.16.1) I always used Mxalloc(size, 0x20 | 2) to allocate global memory (preferably) in ST-RAM. This works for me :-) The question is: is this the proper way to allocate global memory which is shared between TOS applications? When you look at the various documentations which can be found on the internet (Atari Compendium, TOS.HYP), you'll read that the "bit 3" has a special meaning which indicates that the "protection flags" should be evaluated or not. And my experiences tell me that this is not true. Or at least this bit is not needed. Is there a maintained documentation of Mxalloc() as MiNT implements it? (I've read the mint2.pap file in the mint programmer documentation confirms my ideas but dates from 1999.) The internet sources which give bit 3 a special meaning are: Atari Compendium (http://www.fortunecity.com/skyscraper/apple/308/html/gemdos.htm) TOS.HYP (http://www.mbernstein.de/atari/prog/tos/050d05.htm) regards Philipp