[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] Questions about chardev (and ps/2 mouse)
From: |
Brian Wheeler |
Subject: |
[Qemu-devel] Questions about chardev (and ps/2 mouse) |
Date: |
Tue, 05 Apr 2011 14:55:16 -0400 |
I'm trying to disable the ps/2 mouse in favor of the serial mouse
provided by -chardev msmouse since the ps/2 mouse has had lots of
problems with older OSes (OpenStep, OS/2, Win 3.1, etc). I've got a
couple of questions:
1) If I change a VMState something by appending a field (i.e.
"unplugged"), do I have to update version_id? How do the
minimum_version_id{,_old} fields fit in?
2) I've had to hardcode the unplugged value in ps2_mouse_reset since the
call is pretty deep in the call stack, 8042->pckbd->ps2. Ideally, I'd
like to set (*PS2MouseState)->unplugged from qemu_chr_open_msmouse() so
that if the serial mouse is set up the ps/2 mouse would be disabled.
3) When I enable the msmouse (via -chardev msmouse,id=mouse) qemu
segfaults. I've traced it back to the CharDriverSTate for msmouse not
having a valid handler_opaque (it is null). How would I connect that to
the serial port (any of them, but ideally the 2nd one)
Thanks for any hints!
Brian
- [Qemu-devel] Questions about chardev (and ps/2 mouse),
Brian Wheeler <=