Is another VBLANK interrupt triggered while processing VBLANK code ?
In other words : do I have to stop Vints in my VBLANK interrupt routine ?
Sorry if this question sounds stupid, I have to make it clear.
What happens if the VBLANK int code takes too long?
Moderator: BigEvilCorporation
-
- Very interested
- Posts: 86
- Joined: Fri Sep 25, 2015 4:16 pm
Re: What happens if the VBLANK int code takes too long?
I don't remember if that is what will happen in that situation, but one solution is to have your vblank routine set a flag that vblank is active, which will let your main code spin on that flag until VBlank sets it, at which point your vblank logic can occur.
-
- Very interested
- Posts: 3131
- Joined: Thu Nov 30, 2006 9:46 pm
- Location: France - Sevres
- Contact:
Re: What happens if the VBLANK int code takes too long?
You don't need that, when the 68000 takes an interrupt it raises its interrupt level mask to the current interrupt level, meaning that only higher interrupt can interrupt current processing. A V-Int can interrupt H-Int process but not the contrary, also V-Int cannot interrupt another V-Int.