Re: [hatari-devel] _FRB cookie in Falcon emulation

[Uwe Seimet <Uwe.Seimet@xxxxxxxxx>]

Too bad I did not know this some days ago. It would have saved my beta
testers and me quite some time, but anyway ...

As already mentioned there is accelerator hardware which does not require a
patched TOS but sets up Alternate-RAM with a program for the AUTO folder. I
doubt that one of my beta testers is the only user who uses the accelerator
this way.
Saying that, I still understand the motivation for these changes, but the
assumption that there is always a patched TOS when there is a Falcon
accelerator board is not correct.

> no, hatari will do this itself in the case of falcon + tt-ram and not 
> using emutos. see src/cpu/stMemory.c around line 264
> 
> if ( (...)
>          || ( Config_IsMachineFalcon() && TTmemory && !bIsEmuTOS) )
> {
> 
>     if ( TTmemory )
>             STMemory_WriteLong ( 0x5a4 , 0x01000000 + TTmem_size ); 
>     /* ramtop */
>     else
>             STMemory_WriteLong ( 0x5a4 , 0 );               /* ramtop */
>     STMemory_WriteLong ( 0x5a8 , 0x1357bd13 );              /* ramvalid */
> 
> }
> 
> -> so, falcon + tt-ram + tos 4.04 will be handled automatically by 
> hatari to declare this extra tt ram (because tos 4.04 doesn't know how 
> to detect tt-ram, even if it knows how to use it afterward)
> 
> Nicolas
> 
> 
>