|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 keskiviikko 14 tammikuu 2015, Uwe Seimet wrote:
> > On tiistai 13 tammikuu 2015, Uwe Seimet wrote:
> > > > > > --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.
> > Was this with WinUAE CPU core or old UAE CPU core?
> > If former, could you check also old UAE CPU core, just in case
> > (before updating Hatari sources)?
> This was with the WinUAE core. With the old core the behavior is the
> same as with Hatari 1.8.0 and the new core: Pixel garbage with the first
> resolution, the second resolution works fine.
Ok, so the NVDI hang was probably WinUAE core regression, not
due to the larger gap.
I already updated the code to give smaller gap with other than
TT mono resolutions though... If you have time, maybe you could
update Hatari and see whether that afected the WinUAE core hang,
to verify it's actually a WinAUE core issue, and not gap one?
(Nicolas' CPU core change in meanwhile shouldn't affect this
case, they're for 68000 and MMU cases.)