Re: [Freemint-discuss] Ssystem( ) and ColdFire processors

[Vincent R. <vin...@fr...>]

On 23/04/2018 at 19:03, Thorsten Otto wrote:
> The best thing would maybe to set the major cpu id to 1, as that, according to
> the documentation, would indicate a non-m68k processor.

That makes sense.

Key point is: ColdFire is not 680x0.

In EmuTOS for ColdFire, I have even removed the _CPU cookie, as it 
doesn't make sense on a non-680x0 CPU.

But beware at something. The above is true for EmuTOS, where the CPU is 
pure ColdFire without any emulation.

But with FireTOS, the situation is different. The ColdFire is 
*partially* available

- user ColdFire instructions are available (not even fully true, as 
incompatible instruction such as move.b to stack are partially hacked to 
mimic 68000 behaviour)

- but ColdFire supervisor instructions are not available at all, hidden 
by the CF68KLib (remember that *all* programs running on FireTOS 
actually run in user mode, even when they think they have switched to 
supervisor)

In case of FireTOS, the _CPU cookie reflects what the *emulated* CPU is 
supposed to be. Maybe it should be the same for Ssystem(), that would 
make sense. Then provide new *documented* way to add information for 
ColdFire, which can't clash with any 680x0 values.

-- 
Vincent Rivière