Re: [hatari-devel] Videl / VBL interrupt issue in Hatari?

[Mariusz Buras <mariusz.buras@xxxxxxxxx>]

Well, for instance, if your VBL routine would take almost entire frame to execute on real falcon, on Hatari it could be more then one frame to do the same task, so they would overlap.

--
Cheers,
Mariusz Buras.
---
http://sqward.net
http://www.linkedin.com/in/mariuszburas

On 20 January 2014 12:08, Eero Tamminen <oak@xxxxxxxxxxxxxx> wrote:

Hi,

On maanantai 20 tammikuu 2014, Mariusz Buras wrote:
> Perhaps it happens because Hatari is usually slower then real Falcon?

VBL handler is called again before it has finished.

I.e. VBL handler code suddenly got much slower (interrupted by
other things?), after 8 mins of running ok, or something caused
VBL interrupt to happen pre-maturely.

How exactly you were thinking that Hatari's different timings
(it doesn't emulate CPU data cache effects) would cause that?


        - Eero

>
> Cheers,
> Mariusz

>
> > Hi,
> >
> > Douglas is having strange Videl & VBL issue. VBL interrupt
> > handler starts recursing until its stack usage stomps over
> > something important:
> > http://www.atari-
> >
> > forum.com/viewtopic.php?f=68&t=24561&sid=b0e47373736e3702af60c1dec3dd20
> > e8&start=1400
> >
> > This doesn't occur on real Falcon (has never happened there,
> > can be reproduced 100% in Hatari).
> >
> > "It does stop if I don't lower interrupt priority mask in the VBL. It's
> > very
> > strange that the VBL can recurse on top of itself without a loop
> > present, or
> > any jumps. I might even say its borderline not-possible."
> >
> > Any ideas what could cause this with WinUAE CPU core?
> >
> >         - Eero