Does anyone know? Have the Atari guys figured out how to make an efficient emulator, or are they taking the performance hit?
I actually own and use a Firebee on a daily basis. The CPU compatibility issue is addressed in several ways:
1. The CF68KLib. This handles almost all illegal instructions. It does degrade performance to some extent. Currently it runs 68k applications about 2.5 times faster than my 60Mhz Milan060.
2. A software 68k emulator for better-than-060 compatibility when needed. This is based on the Musashi 68k-emulator and allows individual processes to run in separate emulated 68k CPUs. They share memory space with the real CPU, and all OS-calls are of course run in native mode.
3. The OS is compiled for the ColdFire, no issues there.
4. Binaries are patched (move.b xx,-(sp), LineA...) when launched.
Most *applications* are running fine with the CF68KLib. Some needs to be run under the 68k-emulator, and quite a few does not work at all.
What's interesting is that the apps that don't work often does this for other reasons than the CPU. I don't know how it's like in the Amiga world, but in the Atari world there's a lot of applications that make assumptions about screen layout, sound hardware, RAM etc and when you create a new computer it's hard to get these things perfectly backwards compatible. I have a Falcon, a Falcon with a 040 accelerator and a Milan060 (Atari clone) and the problem is always the same - the previous generation of software doesn't run or run with problems.
The Firebee in it's current state is a "GEM-machine". It runs GEM applications fast and stable, about 90% of the stuff that runs on my Milan060 also runs on my Firebee.
I would love to have a fast machine with a "real" 060. But currently there it no such thing. Even when running 68k code the Firebee is faster than the fastest 060 (which I think is a Falcon with a 100Mhz CT60). And the 060 is not without issues either.