From mint-bounce@lists.fishpool.fi Thu Oct 19 18:53:31 2006 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Date: Thu, 19 Oct 2006 19:42:18 +0300 From: "George (HOL, IMAP)" X-Mailer: The Bat! (v3.85.03) Professional Reply-To: "George (HOL, IMAP)" X-Priority: 3 (Normal) Message-ID: <1677101202.20061019194218@hol.gr> To: "'MiNT List'" Subject: [MiNT] Re[2]: 68030 MMU crash course? In-Reply-To: References: <188640904.20061019143010@hol.gr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: ggn@hol.gr 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=-1.0 tagged_above=-50.5 required=7.0 tests=BAYES_00 X-Spam-Level: Hi all, Thanks for the overwhelming amount of replies! The article pointed by Mikro seems to be easy to understand. I'll try some experiments when I have some time. But since one of you (Xavier) asked me to elaborate what I'm trying to do I thought I might as well do that! (I have nothing to hide anyway :) A few months back a very small group of people decided to start patching ST games so that they can be ran off hard drives and furthermore add Falcon compatibility. 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 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!" So I began researching on the MMU. First stop was a program called Backwards, which, as you most will know, makes a lot of games Falcon compatible. It messes around with the MMU so I disassembled that in hopes of understanding what it did. When it became apparent that I wouldn't understand how the MMU is programmed from that example, I posted my question here :) 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! (BTW: I didn't want to bore you with all this in the first place, that's why my first post was rather Laconic!) -- Best regards, George Nakos [From the operation manual for the CI-300 Dot Matrix Line Printer, made in Japan]: The excellent output machine of MODEL CI-300 as extraordinary DOT MATRIX LINE PRINTER, built in two MICRO-PROCESSORs as well as EAROM, is featured by permitting wonderful co-existence such as; "high quality against low cost," "diversified functions with compact design," "flexibility in accessibleness and durability of approx. 2000,000,00 Dot/Head," "being sophisticated in mechanism but possibly agile operating under noises being extremely suppressed" etc. And as a matter of course, the final goal is just simply to help achieve "super shuttle diplomacy" between cool data, perhaps earned by HOST COMPUTER, and warm heart of human being.