[hatari-devel] Some news
Nicolas Pomarède
npomarede at corp.free.fr
Wed Oct 6 22:16:05 CEST 2010
Le 06/10/2010 21:26, Laurent Sallafranque a écrit :
> Hello,
>
> I'm actually working on the main 68000 code (uae code)
>
> I've started to integrate the latest WinUae code to hatari.
> Like this, we'll have a better 680x0 emulation, a much better 68030
> (with MMU) and why not, a 68060 (if we want to emulate the ct60 cards
> and be able to see some recent demos).
>
> We'll also be able to use the precise cycle code they added in the
> latest release.
>
> I'll tell you more when I have something to spread.
>
> Regards
>
> Laurent
>
Hello,
That's good new, but try to keep a version of hatari that can be build
with current uae or with winuae's one committing a new cpu core and
removing the current one from mercurial does not look like a good option
now, we will certainly need months of test/regression before considering
the new core does all the current one does (I know some stack/exceptions
used in some protections are not correctly emulated in winuae ; also
some opcodes (tas for example) work differently).
I think best would be to have a "winuae-cpu" directory in addition to
"uae-cpu" and have some define + flags in cmake to be able to choose the
cpu core at compile time.
I think it would be good also when modifying winuae's sources to not
remove amiga's specific code to put atari's one instead, but to keep
both with some conditionial defines.
eg :
#ifedef HATARI_BUILD
.... <new hatari code>
#else
.... <original amiga/winuae code>
#endif
This way we can keep track of all specific modifications made for hatari
and it will be much easier to backport future winuae's improvements in
hatari.
Many specific code was added to uae's core, adding them back to winuae's
core will not be an easy task.
Nicolas
More information about the hatari-devel
mailing list