Hi,
ok, I think this plan is a good one. It might even be possible to run
several different machines by
starting a single QEMU emulation process. But you need some mechanism to
tell QEMU which machine(s) to run.
Of course, you could add new command line options. MIPS, for example,
could select endianness
automatically in user mode (from ELF format), but not in system mode
when running a complete system
with a firmware loader. So you need some way to tell QEMU that this is a
MIPS CPU with a certain kind
of endianness (the real CPU has a hardware input pin for this, we need
something which replaces this
hardware input pin).
Did you think about using configuration files (XML, YAML, or any other
format) with machine descriptions
(CPU, CPU variant, endianness, network hardware, serial ports, other
hardware features which are
compiled into the code or configured via command line options today)?
Regards
Stefan
Fabrice Bellard schrieb:
Hi,
The long term plan for qemu is to have a single executable for all
machines. If you make a single executable for mips and mipsel, it is
better to select the endianness in the code of the machine itself when
initializing the CPU.
Regards,
Fabrice.
_______________________________________________
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
