Hello All,
I'll try to answer to everybody in single mail and explain my vision of
unified plugin API and why I see them essential.
Yes, I am Bochs developer, but I am more CPU expert and only learning the
devices subsystem and dynamic translation subjects so Bochs is a right place
for me ;) I am
Currently Bochs plugins APCI already begins with such C-language bindings.
But inside the device is C++ based and derives from Bochs device model. It
has the same log writer and debugging interface as any other Bochs module
but nothing more.
Could you look into the Bochs devices code and plugin co
Hi again,
>>It is not a secret that all open source emulators (QEMU, Bochs, Xen) use
>>the same emulated devices and mostly copy-paste their emulation one from
>>another.
>While from my understanding Xen uses qemu's hardware emulation for it's VT
>support, this is not really true otherwise.
>Th
Hello All,
It is not a secret that all open source emulators
(QEMU, Bochs, Xen) use the same emulated devices and mostly copy-paste their
emulation one from another.
I don’t know who originally wrote the device models
but now Bochs and QEMU maintain two similar implementations of the s
