summaryrefslogtreecommitdiffstats
path: root/linux-user
diff options
context:
space:
mode:
authorCorentin Chary2010-07-07 20:57:56 +0200
committerAnthony Liguori2010-07-27 00:36:14 +0200
commitefe556adb75a20ab71f3e5b1c5b19bf045e7953f (patch)
tree1ad2906fd0fd77b5458ac2592a64c4fe4b8d301e /linux-user
parentvnc: tight: remove a memleak in send_jpeg_rect() (diff)
downloadqemu-efe556adb75a20ab71f3e5b1c5b19bf045e7953f.tar.gz
qemu-efe556adb75a20ab71f3e5b1c5b19bf045e7953f.tar.xz
qemu-efe556adb75a20ab71f3e5b1c5b19bf045e7953f.zip
vnc: tight add PNG encoding
Introduce a new encoding: VNC_ENCODING_TIGHT_PNG [1] (-269) with a new tight filter VNC_TIGHT_PNG (0x0A). When the client tells it supports the Tight PNG encoding, the server will use tight, but will always send encoding pixels using PNG instead of zlib. If the client also told it support JPEG, then the server can send JPEG, because PNG will only be used in the cases zlib was used in normal tight. This encoding was introduced to speed up HTML5 based VNC clients like noVNC [2], but can also be used on devices like iPhone where PNG can be rendered in hardware. [1] http://wiki.qemu.org/VNC_Tight_PNG [2] http://github.com/kanaka/noVNC/ Signed-off-by: Corentin Chary <corentincj@iksaif.net> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'linux-user')
0 files changed, 0 insertions, 0 deletions