[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] tt030 memory map

To: Mint List <mint@fishpool.com>
Subject: Re: [MiNT] tt030 memory map
From: Xavier Joubert <xavier.joubert@free.fr>
Date: Fri, 13 May 2005 11:24:26 +0200
Delivered-to: fnaumann@mail.boerde.de
In-reply-to: <42846EDC.5000601@hysteria.sk>
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-id: <mint.lists.fishpool.fi>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
References: <20050513062018.GB20995@hysteria.sk> <Pine.NEB.4.62.0505130852140.20098@wh58-508.st.uni-magdeburg.de> <4284631C.3050008@hysteria.sk> <1115973936.4284693078f26@imp5-q.free.fr> <42846EDC.5000601@hysteria.sk>
Sender: mint-bounce@lists.fishpool.fi
User-agent: Internet Messaging Program (IMP) 3.2.5

Selon Miro Kropacek <mikro@hysteria.sk>:
> 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

References:
- [MiNT] tt030 memory map
  - From: mikro <mikro@hysteria.sk>
- Re: [MiNT] tt030 memory map
  - From: Frank Naumann <fnaumann@boerde.de>
- Re: [MiNT] tt030 memory map
  - From: Miro Kropacek <mikro@hysteria.sk>
- Re: [MiNT] tt030 memory map
  - From: Miro Kropacek <mikro@hysteria.sk>

Prev by Date: Re: [MiNT] tt030 memory map
Next by Date: [MiNT] GCC help
Previous by thread: Re: [MiNT] tt030 memory map
Next by thread: Re: [MiNT] tt030 memory map
Index(es):
- Date
- Thread