The underlying protocol is flexible enough, though only binary at the moment. I
could image a situation were a device driver communicated with the emulation
using it or alternately an application communicated with some hardware and
passed it on to the emulator. As the protocol is quite simple an
Stefan Hajnoczi writes:
> On Wed, May 03, 2017 at 02:20:55PM +, John Bradley via Qemu-devel wrote:
>> Hi
>> I have created a new fork on GitHub https://github.com/flypie/flypie-pi-qemu
>> and an associated project https://github.com/flypie/GDummyPanel the idea as
>> well as getting the Ori
On Wed, May 03, 2017 at 02:20:55PM +, John Bradley via Qemu-devel wrote:
> Hi
> I have created a new fork on GitHub https://github.com/flypie/flypie-pi-qemu
> and an associated project https://github.com/flypie/GDummyPanel the idea as
> well as getting the Original PI emulation working is to
Hi
I have created a new fork on GitHub https://github.com/flypie/flypie-pi-qemu
and an associated project https://github.com/flypie/GDummyPanel the idea as
well as getting the Original PI emulation working is to add some facility for
simulated IO. This is a demonstration of the latest version, r
