From: Yaniv Kaul <ykaul@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Question on QEMU's VNC Server hextile implementation
Date: Sun, 13 Dec 2009 16:06:32 -0500 (EST) [thread overview]
Message-ID: <575929515.1599781260738392519.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <1783738934.1599701260735354287.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
According to the RFB protocol, section 6.6.4 (hextile encoding), regarding the 'ForegroundSpecified' bit, it says: 'If this bit is set then the SubrectsColoured bit must be zero.'.
It doesn't seem QEMU's VNC server does that. In fact, it looks like both bits are set.
I've verified against a different VNC server, and I didn't see this happening.
(it may be a Wireshark dissector bug, of course).
TIA,
Y.
next parent reply other threads:[~2009-12-13 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1783738934.1599701260735354287.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-12-13 21:06 ` Yaniv Kaul [this message]
2009-12-13 23:53 ` [Qemu-devel] Question on QEMU's VNC Server hextile implementation Anthony Liguori
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=575929515.1599781260738392519.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com \
--to=ykaul@redhat.com \
--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).