[uae] New binaries for testing

  • From: Richard Drummond <evilrich@xxxxxxxxxxxxxx>
  • To: uae@xxxxxxxxxxxxx
  • Date: Tue, 19 Apr 2005 11:43:17 -0500

Hi All

I've made some changes to the timer code in E-UAE with the following aims in 

a) To allow the user to choose between using a CPU-specific timer (when one is
   available) or a generic timer for E-UAE synchronization purposes.
b) To remove the need to calibrate the CPU-specific timer when it's used (and
   so allow faster start-up and better accuracy).

On x86 platforms, the option 'x86.use_tsc' is now supported. Set this to 'yes' 
to use the CPU's time-stamp counter; set to 'no' to use a generic timer 
(currently 'gettimeofday()'). It defaults to 'yes'.

Similarly on PPC platforms, the option 'ppc.use_tbr' has been added to 
enable/disable use of the PPC's timebase register for timing. Again the 
default is to enable it. 

In general, you'll want to enable the CPU-specific timer because using it 
involves a much lower overhead than using a generic timer API. However, on 
x86 machines that do power-saving by scaling the CPU frequency, using the TSC 
for timing is problematic because reducing the clock speed also reduces the 
TSC frequency.

On OS X/DarwinPPC and AmigaOS4 (with AmigaONE hardware only not classic Amiga 
hardware) hosts, E-UAE no longer calibrates the timebase frequency itself and 
instead gets the timebase frequency from the operating system,

New binaries for testing at:

Currently, Linux, OS X and AmigaOS4 binaries have been built because these are 
the platforms most affected by these changes, but give me a shout if you want 
something else.

As usual, these changes are also in CVS if you want to play with the source 
code yourself.


Other related posts: