Hi Yan,
Thank you for the information. I am rather new to Windows Driver
development and learning as I go, so this may take some time, but since
the driver only needs to perform very basic functions I do not see this
as being too much of a challenge.
-Geoff
On 2017-10-15 22:14, Yan Vugenfir
On 2017-10-15 23:24, Yan Vugenfirer wrote:
On 15 Oct 2017, at 15:21, ge...@hostfission.com wrote:
Hi Yan,
Thank you for the information. I am rather new to Windows Driver
development and learning as I go, so this may take some time, but
since the driver only needs to perform very basic functi
On 2017-10-17 02:20, Eric Blake wrote:
On 10/15/2017 04:32 AM, geoff--- via Qemu-devel wrote:
Hi All,
I am writing some code that needs to share a block of ram between a
Windows guest and Linux host. For this I am using the ivshmem device
and
I have written a very primitive driver for windows
This allows guest's to correctly reinitialize and identify the mouse
should the guest decide to re-scan or reset during mouse input events.
Signed-off-by: Geoffrey McRae
---
hw/input/ps2.c | 4
1 file changed, 4 insertions(+)
diff --git a/hw/input/ps2.c b/hw/input/ps2.c
index 06f5d2ac4a..6
This fixes an issue by adding bounds checking to multi-byte packets
where the PS/2 mouse data stream may become corrupted due to data
being discarded when the PS/2 ringbuffer is full.
Interrupts for Multi-byte responses are postponed until the final
byte has been queued.
These changes fix a bug w
This fixes an issue by adding bounds checking to multi-byte packets
where the PS/2 mouse data stream may become corrupted due to data being
discarded when the PS/2 ringbuffer is full.
Interrupts for Multi-byte responses are postponed until the final byte
has been queued.
These changes fix a bug w
This allows guest's to correctly reinitialize and identify the mouse
should the guest decide to re-scan or reset during mouse input events.
When the guest sends the "Identify" command, due to the PC's hardware
architecutre it is impossible to reliably determine the response from
the command amongs
This allows guest's to correctly reinitialize and identify the mouse
should the guest decide to re-scan or reset during mouse input events.
When the guest sends the "Identify" command, due to the PC's hardware
architecutre it is impossible to reliably determine the response from
the command amongs
This fixes an issue by adding bounds checking to multi-byte packets
where the PS/2 mouse data stream may become corrupted due to data being
discarded when the PS/2 ringbuffer is full.
Interrupts for Multi-byte responses are postponed until the final byte
has been queued.
These changes fix a bug w
