|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 12/01/2015 23:51, Eero Tamminen a écrit :
On maanantai 12 tammikuu 2015, Uwe Seimet wrote:
Uwe, could you check whether NVDI works with these both:
--vdi-width 800 --vdi-height 600 --vdi-planes 4
--vdi-width 1920 --vdi-height 1080 --vdi-planes 1
With the first resolution NVDI hangs after displaying its startup
message, with the second resolution it work.
Ok, this is as I feared.
Does the hanging resolution work if you use earlier
Hatari version, e.g. v1.8 release?
I.e. is the issue larger memtop->phystop gap
(needed for TT memory detection) or is NVDI just
not handling larger color resolutions that well...
as written previously, I don't think this is related to TT RAM. ST RAM
detection will fail with high vdi resolution even if you use 14 MB RAM
and no TT RAM.
In all cases, memtop and phystop ($42e and $436) are limited to ST RAM
space, if you have TT RAM, it's only refered in $5A4. So the "gap"
between memtop and phystop should be ST RAM related.