|Re: [hatari-devel] Re: RAM detection issue with VDI (was HDDriver issues with WinUAE CPU core)|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
Le 11/01/2015 16:41, Eero Tamminen a écrit :
On sunnuntai 11 tammikuu 2015, Nicolas Pomarède wrote:
Le 11/01/2015 12:34, Nicolas Pomarède a écrit :
> I agree, I saw this part of the code too, and I think something must
> be wrong when using VDI (maybe screensize should be rounded to
> something else, a multiple of 0x8000 ?)
Btw: if you use "--conout 2" with VDI mode and TT-ram, you notice
that TOS3 gives "infinitely" long ST-ram checking bar at TOS boot.
When memtop is 32k aligned, TOS3 detects TT-RAM, so I commited
maybe there's a misunderstanding, but as I wrote previuously, the
problem is also present when there's no tt ram ; the bar will loop on st
ram detection anyway and also since at least hatari 1.4.1, even with old
uae cpu core, so this is unrelated to the new/old cpu.
I tested with your patch on memtop, and the problem is still there, st
ram bar still loop forever :(
There's not much point in using VDI mode with smaller amounts of RAM.
VDI mode is used to get larger screen and that takes memory, with 512k
you don't enough memory left to run the applications.
That was just an example to point that it happen with any ST RAM config,
not just 14 MB ; even if there's not enough ram for apps, it should at
least pass the detection at boot.