Re: [hatari-devel] Re: RAM detection issue with VDI (was HDDriver issues with WinUAE CPU core)

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

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.


	- Eero

> 
> Take care
> 
> Uwe
> 
> > Hi,
> > 
> > The memory test appears to work fine now on my machine, but a
> > resolution of 1280x1168 (TT mode, monochrome) pixels does not work
> > anymore now. There is pixel garbage now at the bottom of the screen
> > during the memory test, but the more serious problem is that after the
> > memory test the system crashes with two bombs. Before there was
> > neither pixel garbage nor a crash.
> > Yes, I know that 1280x1168 pixels is not a solution supported by a real
> > TT, but it was working fine until the latest changes from a few minutes
> > ago. Any resolution with a screen height of more than 960 pixels does
> > not seem to work anymore.
> > 
> > Take care
> > 
> > Uwe
> > 
> > > Hi,
> > > 
> > > On sunnuntai 11 tammikuu 2015, Nicolas Pomarède wrote:
> > > > Le 11/01/2015 17:53, Roger Burrows a écrit :
> > > > >> This is pretty bogus for a TT or a Falcon ... and I believe this
> > > > >> issue was related to running TOS 3.06, so must have been TT
> > > > >> emulation ...
> > > > > 
> > > > > Just to make it 100% clear what I was referring to: only
> > > > > ST-compatible resolutions use 32K.  TT high, medium, low & all
> > > > > Falcon resolutions use more memory.  So always setting phystop
> > > > > to memtop+32K does not seem right ...
> > > > 
> > > > ok, but in that case that's not what the actual code does : it sets
> > > > memtop to *at least* 32k. If screensize is higher than 32k in vdi,
> > > > then it's taken into account.
> > > 
> > > Roger was referring to phystop.   But old TOS versions didn't work
> > > if gap between memtop -> phystop is larger.
> > > 
> > > > Still, this doesn't seem to be enough to fix it.
> > > 
> > > Please check the updated fix:
> > > http://hg.tuxfamily.org/mercurialroot/hatari/hatari/rev/036a41cfbc56
> > > 
> > > What value works, seems both TOS & machine specific
> > > (in case of EmuTOS).
> > > 
> > > 	- Eero