Get into Fastram you naughty EXEC

[Piru]

I run MuFastZero in my startup-sequence and my expansion.library in still not in fast ram. I expect there is a good reason for this. Probably because chip ram is always at the same location and doesn't go away at reset which makes life at startup much easier.

Actually AFAIK it is. You just can't see it from the address (it's remapped with MMU).

[Piru]

@Piru

Interesting. Obviously, with MAPROM, one copy of the expansion.library would be in fast ram.

Actually it wouldn't. MAPROM just moves the ROM to fast memory. It doesn't actually change the way the ROM itself works. So expansion.library, exec.library and supervisor stack will end up to same memory regardless if you have enabled MAPROM or not.

My expansion.library memory address ($46CC) shows up as being in chip memory in Scout.

$0-$200000 chip memory
$F00000-$1000000 motherboard ROM

The MMU would have to map some of chip memory somewhere else and then fast memory to the old chip memory location for the expansion.library being used to be in fast ram. I highly doubt that. It looks to me like the expansion.library is actually in chip ram.

That's how it works, except that only chip memory needs to be mapped to fast memory. Since the expansion.library doesn't know it has been remapped elsewhere it doesn't need to have mapping the other way.

[Piru]

Hi Piru,

Is it even a good idea to try and map the expansion.library to FASTRAM?

I assume that BlizKick doesn't do it is because it's a bad idea?

By conventional means it is a bad idea. With MMU it is possible, assuming at the whole MMU page worth of chip memory is allocated for it. I believe this is what the "prepare" tool in mmulib method is doing.

However, expansion.library is rarely used so it doesn't really matter that much. exec.library and supervisor stack is much more important to have in fast mem, and this is possible even without mmu.library.