|Re: [hatari-devel] TOS bootup tester results|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
Le 26/06/2015 22:15, Eero Tamminen a écrit :
What if in WinUAE core we default to 32-bit addressing on TT,
as with that RAM detection seems to work in all cases?
Do you think that would cause issues somewhere else?
I don't know, that would need more tests to be sure there's no side
effect, I'd rather leave it for now and see after 1.9 is released.
On perjantai 26 kesäkuu 2015, Nicolas Pomarède wrote:
Le 26/06/2015 00:55, Eero Tamminen a écrit :
Enabling MMU doesn't help, but enabling 32-bit addressing makes TOS v3
work also with 4MB of RAM. I.e. it was actually 32-bit addressing,
not TT-RAM, that helped.
Why things work without 32-bit addressing when there's >4MB of ST-RAM?
memory above 4 MB was not a standard MMU confirguration. In that case, a
patched version of the TOS is needed (or some programs in auto/ that
will reconfigure the TOS memory map).
In Hatari, we force a few system variables in stMemory.c to skip the
hardware ram detection. When we skip the ram detection, I guess we also
skip some parts of the boot process that requires 32 bit and that once
the ram detection is done (or skipped), TOS doesn't try to access 32 bit
address, only the ram that was declared in TOS.