|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
On sunnuntai 11 tammikuu 2015, Nicolas Pomarède wrote:
> Le 11/01/2015 21:46, Eero Tamminen a écrit :
> > On sunnuntai 11 tammikuu 2015, Uwe Seimet wrote:
> >> Looks as if it's NVDI that's crashing.
> > I get crash also without NVDI.
> > It seems that with real TOS:
> > * VDI mode works only when gap is is same (or smaller)
> > than the largest real HW resolution they support.
> > * Memory detection works only when gap is the right one.
> > I've commited additional check for this.
> > I.e. with that large resolution you don't get correct
> > memory detection, just VDI mode. Only with smaller VDI
> > mode, you get also correct memory detection.
> Using uwe's hatari.cfg that I re-attach here, I still get the infinite
> memory bar detection when vdi is on.
> Can you try running :
> ./hatari -c ../hatari_vdi.cfg --tos ~/Emul/ST/steem/tos/tos306fr.img
> It uses 1280x1168
Yes, that's the expected behavior.
If your memtop<->phystop gap is larger than largest real TT screen
size (1280x960@1bpp = 150k), you either get TOS crash, or memory
size detection failure, depending on what kind of gap you use.
TOS crash is worse, so I limit gap with TOS3 to 150k.
If one keeps resolution smaller than that, one can still have
both memory detection and more relaxed resolution selection than
what TT TOS supports (e.g. smaller resolutions where screen size
with statusbar matches some monitor resolution better).
(Hatari allows resolutions up to 300k, after that TOS/apps starts
to get more crashy regardless of gap size.)
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
If not, I need to set the gap smaller regardless of what the TOS
would work with...