From mint-bounce@lists.fishpool.fi Fri May 13 11:42:50 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <1115976266.4284724aab6fd@imp5-q.free.fr> Date: Fri, 13 May 2005 11:24:26 +0200 From: Xavier Joubert To: Mint List Subject: Re: [MiNT] tt030 memory map References: <20050513062018.GB20995@hysteria.sk> <4284631C.3050008@hysteria.sk> <1115973936.4284693078f26@imp5-q.free.fr> <42846EDC.5000601@hysteria.sk> In-Reply-To: <42846EDC.5000601@hysteria.sk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 User-Agent: Internet Messaging Program (IMP) 3.2.5 X-Originating-IP: 212.234.144.141 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: xavier.joubert@free.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=0.5 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00 X-Spam-Level: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id j4D9gnH0003637 Selon Miro Kropacek : > Probably meaned to list.. It was. Sorry for double-post. > I can check just Falcon030 since I don't have a TT :) TOS 3.x (TT) and 4.x (Falcon) use the exact same MMU setup. > Hmm, so how it is? I have a mmu map of Falcon030, it seems understable, > 0xffff0000 -> 0x00ffxxxx, cache inhibit things and so on... so differs > TT so much? Looks like your better than me. It took me some days to fully understand the Transparent Translation Registers setup. ;) Xavier