[hatari-devel] WinUae CPU for hatari

Laurent Sallafranque laurent.sallafranque at free.fr
Tue Nov 2 09:00:41 CET 2010


Hello,

fpu.c now compiles.

All WinUae CPU compiles now.

I'm now in :
[ 69%] Building C object src/CMakeFiles/hatari.dir/m68000.c.o


>  Defining "L" empty didn't work?

I don't understand how you want it :
(  "#define L"     ?)

If I do something like this, lines like "ASL" will become "AS", no ?

Regards

Laurent


Le 01/11/2010 23:57, Eero Tamminen a écrit :
> 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
> _______________________________________________
> hatari-devel mailing list
> hatari-devel at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/hatari-devel
>
>
>    




More information about the hatari-devel mailing list