From mint-bounce@lists.fishpool.fi Thu Oct 19 20:42:01 2006 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=drlCTJSiR3bjj+8z7KRQd6ERxJxpg4nI1Mm2N6n4VkEXHX2xmjh9EccZtiZ7HxricbCXmAKohejbyZ61xUroqK2bEKFi7ZhBE+UKQywbZ+0d8i+Fd5Lbfw1t/K1lvaCPHStWfucOR+LbZycsck3kXpIQbvHKJ4+oV5wuxKQRv14= Message-ID: Date: Thu, 19 Oct 2006 20:32:59 +0200 From: MiKRO To: mint@fishpool.com Subject: Re: [MiNT] Re[2]: 68030 MMU crash course? In-Reply-To: <1677101202.20061019194218@hol.gr> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_189571_23160433.1161282779366" References: <188640904.20061019143010@hol.gr> <1677101202.20061019194218@hol.gr> X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: miro.kropacek@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: 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.2 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00, HTML_MESSAGE X-Spam-Level: ------=_Part_189571_23160433.1161282779366 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline > As you can imagine we run into pretty weird problems at points, one > of them > being the shadowing of the YM2149 registers on the ST (not present > on the FYI, this is already done by TOS. Even on ct60 TOS Didier did this. So no problem here (whole 0x00FFxxxx area is already "mirrored" on 0xFFFFxxxx) Falcon). The course of action we're following now is to patch the offending > code > and get on with it, but this can prove tiresome and repetitive. Then we > thought "Wait a minute, if we can make the MMU transparently map areas like that to > the > Falcon registers, we won't have to patch anything at all!" can i ask why do you find this as easier solution? Patching the binary is a question of one clever script/program which search for 0xffffxxxx in code segment with some exceptions maybe... but it could be automated for sure a lot. > Anyway, hope you didn't all go to sleep! You can check our > progress at > http://www.tphf.karoo.net/dbug/falcon.htm. Any comments or criticism is > welcome! I wish you good luck. What rule do you use to choose which game will be ported? I think a lot of games doesn't need to be ported since... they are crap. There is maybe 40-50 cool ST games which are worth to do it... -- MiKRO / Mystic Bytes ------=_Part_189571_23160433.1161282779366 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline


  As you can  imagine  we  run into pretty weird problems at points, one of them
being  the  shadowing  of  the  YM2149  registers  on the ST (not present on the

FYI, this is already done by TOS. Even on ct60  TOS Didier did this. So no problem here (whole 0x00FFxxxx area is already "mirrored" on 0xFFFFxxxx)

Falcon). The course of action we're following now is to patch the offending code
and  get on with it, but this can prove tiresome and repetitive. Then we thought
"Wait  a minute, if we can make the MMU transparently map areas like that to the
Falcon registers, we won't have to patch anything at all!"

can i ask why do you find this as easier solution? Patching the binary is a question of one clever script/program which search for 0xffffxxxx in code segment with some exceptions maybe... but it could be automated for sure a lot.


  Anyway,  hope  you  didn't  all  go  to  sleep!  You can check our progress at
http://www.tphf.karoo.net/dbug/falcon.htm. Any comments or criticism is welcome!

I wish you good luck. What rule do you use to choose which game will be ported? I think a lot of games doesn't need to be ported since... they are crap. There is maybe 40-50 cool ST games which  are worth to do it...


--
MiKRO / Mystic Bytes ------=_Part_189571_23160433.1161282779366--