Sure, it COULD! As it worked fine on Amiga and ColdFire Evaluation Boards.Eero Tamminen wrote:I wonder whether EmuTOS will eventually cover a larger number of the m68k machines simulated by MiST (MachinTos, Sinclair QL)?
But the case of Amiga was lucky: it was possible to display something because the Amiga hardware is able to create a video mode compatible with ST-High (even if it is uglyly interlaced). Resolution is not a problem, but pixel format (1 bit for each pixel, from high-bit to low-bit) is required for current EmuTOS VDI.
If the video is not compatible, then you will have to live with a simple serial port to run text-mode TOS programs (like ColdFire EVB). Or write a special fVDI driver for the new video hardware, as I recently did with WinUAE and Vampire/SAGA.
The only requirement to port EmuTOS to something else is to have a 680x0/ColdFire CPU and enough RAM (256 KB is enough). Then you can easily port EmuTOS to new hardware. Then of course, additional drivers for new hardware will have to be written.
Well, I would love to see EmuTOS running natively on ARM / Raspberry Piwongck wrote:if I am force sensitive and able to do that.... I would mind trick Vincent & Roger to make an ARM Emutos
As it has already been said, this has already been done for ColdFire. But ColdFire is very similar to 680x0, that's much easier. And despite that, it had been a lot of work to port EmuTOS to ColdFire, mainly to handly written assembler sources, and some CPU-specific code. The result can be seen on the FireBee: a perfectly working EmuTOS, but only able to run programs recompiled for ColdFire.
For ARM or x86, it would be much more complicated. Several EmuTOS parts require a Big Endian CPU. Many parts (if not all) written in C require that the "int" type is 16-bit wide, I'm not sure that GCC can support that on those processors. And of course, all the assembler sources would have either to be converted to C, or to the target assembler.
Conclusion: It is very unlikely that a native EmuTOS for something else than 680x0 / ColdFire appears soon... or even later