[hatari-devel] Timer-D CPU usage in latest Hatari

Thomas Huth th.huth at gmx.de
Mon Jul 13 23:28:37 CEST 2009


On Mon, 13 Jul 2009 23:13:12 +0300
Eero Tamminen <eerot at users.berlios.de> wrote:

> On Sunday 12 July 2009, Eero Tamminen wrote:
> > Currently Timer-D patching can be controlled only from the GUI &
> > config file.  Because of [1] & [2], I think there should be a
> > commandline option for it too, maybe:
> >   --patch-timerd <boolean>  Enable for much improved performance
> >
> > It's performance impact should also be highlighted better in the
> > manual. Maybe I should add an "How to speed up Hatari performance"
> > section to the manual (e.g. the www-site FAQ doesn't mention
> > Timer-D at all)?

When the WWW page was created, the Timer-D patch wasn't an option yet,
but it was hard-wired to be always enabled. So you can add it there,
too, if you want.

> Added the documentation:
> http://hg.berlios.de/repos/hatari/raw-file/tip/doc/manual.html#Performance

Thanks, that's a good idea.

> What about the option?

Fine for me, please add it!

> PS. I noticed that the manual still claims these experimental:
> ------
> experimental support for RS232
> experimental MIDI output support (no MIDI input/through support)
> ------
> I guess "experimental" can be removed?  E.g. MIDI input and output
> work fine and I think MIDI through works too (are there any musicians
> on the list?). If I remember correctly, somebody sent RS232
> improvements, so I assume that's also tested & working fine now...

Well, I wouldn't call those features "rock solid", but since there are
also hardly any complains on the mailing list, I also think we could
remove the "experimental" statement here.

 Thomas



More information about the hatari-devel mailing list