In message <20210825223652.GL31179@chiark.greenend.org.uk>
Theo Markettos <theo@markettos.org.uk> wrote:
>> This would give you a reasonable emulation of a more modern platform more
>> suitable for new software, and is a hell of a lot better than the idea of
>> forking RPCemu (since the relevant changes would never be mainlined) to
>> weld in ARMv7 and the like.
> I agree: RPCEmu is designed to be a fixed emulation of a fixed piece of
> hardware from a historical period. If what you want is a way to run modern
> RISC OS on modern hardware, there are other ways to go about it.
I agree completely too.
My point - before the drama - was more on more integration features (à la
hostfs) - perhaps with some only for RISC OS 5 (as we have its source
code). Things that we will never probably see on QEMU.
I have a tool to add some features to RPCEmu, a very crude way. IMHO, it
would be probably better to add a virtual podule + support functions on
the host side, but RPCEmu does not provide a plug-in functionnality. Hint:
we use TCC as side compiler for all our plug-in interfaces at work, so
people have the plug-in feature and the tool to make some very easily.
IMHO, ARMv7 support in RPCEmu is just irrelevant.
On the QEMU side: we have already RISC OS on Linux, that relies (partly)
on unpatched QEMU and permits to uses RISC OS on any Linux or ChromeOS ARM
device... at native speed. Perhaps RISC OS on Linux already solved the
problems that prevent RISC OS to work on QEMU 'the classic way'? (that's
just a question)
I remember some already managed to deploy RISC OS on Linux on AWS ARM
instances. But native RISC OS VM would be cool too :)
David
_______________________________________________
RPCEmu mailing list
RPCEmu@riscos.info
http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
No comments:
Post a Comment