From: Erik Rull <erik.rull@rdsoftware.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] bad USB tablet update rate on qemu-1.0
Date: Mon, 19 Dec 2011 22:33:02 +0100 [thread overview]
Message-ID: <4EEFAD8E.8050509@rdsoftware.de> (raw)
Hi all,
coming from qemu 0.14 the usbdevice tablet update rate gets really bad in
qemu-1.0 with the same guest.
The cursor more jumps with some delay than moving smoothly.
What could be the reason? Are there tablet options that might remove the
jumping?
Best regards,
Erik
next reply other threads:[~2011-12-19 21:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 21:33 Erik Rull [this message]
2011-12-19 21:48 ` [Qemu-devel] bad USB tablet update rate on qemu-1.0 Anthony Liguori
2011-12-19 21:55 ` Erik Rull
2012-01-04 23:17 ` Erik Rull
2012-01-18 21:28 ` Erik Rull
2012-01-18 21:46 ` Erik Rull
2012-01-19 16:40 ` Erik Rull
2012-01-19 16:57 ` Andreas Färber
2012-01-19 19:15 ` Erik Rull
2012-01-20 9:09 ` Andreas Färber
2012-01-20 12:25 ` Erik Rull
-- strict thread matches above, loose matches on Subject: below --
2012-01-23 8:57 erik.rull
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=4EEFAD8E.8050509@rdsoftware.de \
--to=erik.rull@rdsoftware.de \
--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).