qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Brian Wheeler <bdwheele@indiana.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Questions about chardev (and ps/2 mouse)
Date: Tue, 05 Apr 2011 14:55:16 -0400	[thread overview]
Message-ID: <1302029716.31961.24.camel@nibbler.dlib.indiana.edu> (raw)

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

             reply	other threads:[~2011-04-05 18:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 18:55 Brian Wheeler [this message]
2011-04-05 19:36 ` [Qemu-devel] Questions about chardev (and ps/2 mouse) Brian Wheeler
2011-04-05 20:29 ` Anthony Liguori
2011-04-05 20:45   ` Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1302029716.31961.24.camel@nibbler.dlib.indiana.edu \
    --to=bdwheele@indiana.edu \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).