Re: [hatari-devel] TT mono mode Timer-C problem

[Laurent Sallafranque <laurent.sallafranque@xxxxxxx>]

Hi,

That's a big question I have also in mind since a few weeks, but as for 
now the priority is on the ST demos debugging, I didn't want to bother.

I don't like the fact to divide cycles by 2 or 4 to change the CPU 
speed, as timers are impacted.
It may explain the difficulty to synch well the crossbar in all cpu 
spped modes and same for the DSP.

I would enjoy to have a normal cycles CPU with correct cycles in all 
case and VBL timings changing according to the real number.
The timers would be "static" 500 Khz, 25 Mhz, 32 Mhz, ...

Let's see this after the 1.6

Nicolas, I don't think I'll have to change more things before the 1.6, 
so, you can release as it is for the falcon part for now.
(There's still too much work on the 68030 cycles to expect something in 
the next week).

Regards

Laurent


> Hello
>
> yes, it's a known limitation that at the moment the interrupt events 
> are expecting the cpu clock to be 8 MHz. If you use 16 or 32 MHz, 
> interrupts won't be good.
> This will be fixed some day, as it can also impact falcon mode, but 
> for now all the interrupts events are "locked" to the cpu freq 
> (instead of the master bus freq on a real ST/TT/Falcon)
>
> I will take a look, it should be possible to add a patch that improve 
> this without too much damages.
> Are you using the devel version with mercurial ?
>
> Nicolas