> Think of it this way: Work doesn't cause the CPU clock to tick. Causality runs the
> other way: clock cycles are what drive the CPU. When in a suspended state, on each
> clock cycle, the CPU evaluates whether a "wake-up" condition has been met (e.g., an
> external signal, an interrupt, or some on-chip timer expiring). In your case, it's an
> external interrupt. If this hasn't happened, it will remain in the same state.
Right. If the CPU is suspended, the only difference from normal is that no opcodes are emulated on each clock. (This of course greatly reduces the emulation load on the host's CPU). Time still happens for timers and screens and so on.
|
Index 
Flat 
Re: EmuTimer question
Reply
