[hatari-devel] WinUae CPU for hatari

[Eero Tamminen]

Hi,

On Tuesday 02 November 2010, Laurent Sallafranque wrote:
> I've uploaded some files.
> This just let newcpu.c to compile.

Defining "L" empty didn't work?


> Next step is fpp.c to compile.
...
> I think there'll be soon 2 problems :
>
> 1) We'll need to adapt all these files to our own needs.
> So compatibility with original files will decrease (I think at newcpu.c
> file for example).
>
> 2) We'll need to change some parts of hatari's code that won't allow
> compatibility between oldcpu and newcpu (except if we include lot's of
> ifdefs but code may become too heavy and horrible to read).
>
> I think at old variable "cpu_level" used in hatari's GUI for example.
> It seems that this variable doesn't exist anymore and is replaced by :
> cpu_model
> So, we'll have to modify the GUI to allow new cpus, mmus, ..., or create
> a new directory for new parameters, or stop the old branch, ...

cpu_level variable is used by UAE CPU emulation, Hatari itself uses
cpu_level only in two places:
./m68000.c:     changed_prefs.cpu_level = ConfigureParams.System.nCpuLevel;
./gemdos.c:             if (currprefs.cpu_level > 0)

Otherwise it uses value from the ConfigureParams.System struct.  I think
mapping that to whatever WinAUE uses should be fairly isolated in Hatari
code...


	- Eero