From: zitu <zitu@free.fr>
To: qemu-devel@nongnu.org, zitu <zitu@free.fr>
Subject: Re: [Qemu-devel] Current state of RFB patch
Date: Tue, 22 Mar 2005 09:15:39 +0100 [thread overview]
Message-ID: <1111479339.423fd42bb7f09@imp5-q.free.fr> (raw)
In-Reply-To: <1111410939.423ec8fbe3365@imp5-q.free.fr>
[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]
Thanks Johannes
> PS: it could be interesting then to have qemu+vnc running on colinux, and
> get a bit more performance than the std qemu on windows hosts.
sorry for the confusion. What I meant was to get qemu+vnc+kqemu running on
a colinux process, on a Windows host. As you know, kqemu is not yet
available on windows host. That's what I meant as a speed improvement.
I'm hoping that the mouse issues might be linked to a speed bottleneck
between the slowness of qemu without kqemu and the VNC protocol.
Regarding your latest patch, it does not work straight out of the box
on windows hosts. Even with mouse acceleration removed, the calibration is
not there: there's a huge difference between the true location of the mouse
and the one inside vnc... I can still see lots of latency between the slow
move I do and the moment the mouse reacts inside qemu. :(
The mouse calibration which I could call before is not working CTRL-ALT-M :(
To compile successfully, I had to modify for mingw32 the file
"keysym_adapter_vnc.h". rfb9 also needed this. I attached the
file to this email. Maybe this is what is causing some of my keyboards
problem, especially when I switch to the qemu console mode (CTRL-ALT-2).
I've difficulties to come back to the std qemu window inside VNC.
Overall, the mouse looks more responsive than last time. It's still positive!
I'll do some more checks. But no time yet for a colinux check.
Thanks again.
Zitu
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
[-- Attachment #2: keysym_adapter_vnc.h.gz --]
[-- Type: application/x-gzip, Size: 4374 bytes --]
prev parent reply other threads:[~2005-03-22 8:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 18:43 [Qemu-devel] Current state of RFB patch Andreas Bollhalder
2005-03-20 21:55 ` Johannes Schindelin
2005-03-21 13:15 ` zitu
2005-03-21 19:50 ` Johannes Schindelin
2005-03-21 20:14 ` use.reply-to.address
2005-03-21 20:26 ` Jim C. Brown
2005-03-21 20:59 ` Struan Bartlett
2005-03-22 1:13 ` Johannes Schindelin
2005-04-01 16:45 ` Andreas Bollhalder
2005-03-22 6:46 ` Brad Campbell
2005-03-22 11:53 ` Andreas Bollhalder
2005-03-22 8:15 ` zitu [this message]
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=1111479339.423fd42bb7f09@imp5-q.free.fr \
--to=zitu@free.fr \
--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).