[hatari-devel] Hatari options?

Eero Tamminen eerot at users.berlios.de
Tue Mar 1 22:51:14 CET 2011


Hi,

On tiistai 01 maaliskuu 2011, Nicolas Pomarède wrote:
> Le 01/03/2011 20:56, Eero Tamminen a écrit :
> > Attached patch would do that + put Laurent's additional WinAUE options
> > under separate heading + re-order some other things more logically.
> 
> I agree with adding most options you put, except :
> 	--cpu-exact
> 	--addr24  (typo : you put 42-bit mode in the man)

The names of the options are from Laurent's earlier WinUAE changes,
in the patch I just moved then under their own heading in options output
+ fixed their descriptions to conform better with other options
descriptions.

These options have been in Hatari code since last November when Laurent
added WinAUE code.  :-)


> With WinUAE, there're many more modes than just cpu-exact : better
> prefetch, better exceptions, better cycle for micro code, so adding a
> bool option will not be enough.
>
> Also we already have a "--compatible" option ; I think it would not be
> clear for the user what is the effect of "exact" compared to
> "compatible" (in theory, if the cpu emulation is "compatible" with real
> cpu, then it should be "exact").

I was thinking that "--cycle-exact" would have been better option
name, at least based on its description. :-)

I've understood that the  (by default enabled) "--compatible" option is
supposed also to make the old UAE core also (more) cycle exact.
What that option actually does with the WinAUE core?


> I'd rather have a new parameter "--cpu-emulation" for example that could
> take several values : simple, cycle-precise, ...

So these prefetch etc settings aren't independent options, but dependent
on each other?


> Those are just some naming examples and it would encompass both
> --compatible and your --cpu-exact proposition ; but I think we should
> wait for a more advanced implementation of WinUAE core (that is having a
> working replacement for uae core in STF mode) before deciding on what
> values to add for this option.
> 
> Regarding --addr24, I'm not sure we have any real case for this now ; so
> better wait for above point to be solved and add both parameter at the
> same time.
>
> I think it would be counter productive to add some options now, while we
> don't have enough "experience" on what will really be used in the end in
> WinUAE and the effect it can have on ST/Falcon emulation (it would be
> annoying to have some parameters in Hatari 1.5 for example, then notice
> in Hatari 1.6 that those parameters need to be changed ; not very good
> for the user to have changing parameters on each release)

I agree, they need to be fixed before the release.


	- Eero



More information about the hatari-devel mailing list