From mint-bounce@lists.fishpool.fi  Wed Aug 10 12:02:30 2005
X-Original-To: fnaumann@mail.boerde.de
Delivered-To: fnaumann@mail.boerde.de
Date: Wed, 10 Aug 2005 12:01:04 +0200
From: mikro <mikro@hysteria.sk>
Cc: Mint list <mint@fishpool.com>
Subject: Re: [MiNT] what's wrong with this code?
Message-ID: <20050810100104.GB29857@hysteria.sk>
References: <20050810084953.GA29857@hysteria.sk> <42F9C8C7.6040602@klockars.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <42F9C8C7.6040602@klockars.net>
User-Agent: Mutt/1.4.2.1i
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-To: mint-bounce@lists.fishpool.fi
X-original-sender: mikro@hysteria.sk
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=-1.0 tagged_above=-50.5 required=7.0 tests=AWL,
 BAYES_00
X-Spam-Level: 


> Why?
>
for speed. i guess Super() is much slower than simple trap call.
 
> That is not supposed to work from user mode on Atari hardware. The 
> bottom few kbyte (don't remember exactly, but at least past the system 
> variables, so probably until $800 or so) are protected by the hardware.
>
of course, i know this fact. that $80.w move i do in supervisor.
 
> You're doing this on a CT60, right? I guess it does something (remap low 
> memory or similar) that makes this possible in the normal case.
>
as long as you don't switch to SV it isn't possible on anything, that's
clear
 
> more overhead). The last one would allow you to add your own Trap #0 
> handler safely (well, at least unless you have turned on maximum 
> protection in MiNT).
>
thanks for tip, but i fear it wont help since there's no problem in handler
vector setting but with the application of it.
 
> MiNT with memory protection should set the MMU up to protect that memory 
> no matter what the hardware does.
> 
> But it really "shouldn't" work in the other cases either. See above.
> 
as i wrote, setting the $80 isn't the issue. if i disable code that calls
trap #0, it works. so that's the reason why i'm so confused with that MP
(non)functionality...

-- 

---------------------------------------------------------------------------
MiKRO         Atari XE/XL/Mega STE/Falcon060         http://mikro.atari.org
---------------------------------------------------------------------------


