summaryrefslogtreecommitdiffstats
path: root/docs/interop/vnc-ledstate-Pseudo-encoding.txt
diff options
context:
space:
mode:
authorPaolo Bonzini2017-06-06 16:55:19 +0200
committerPaolo Bonzini2017-06-15 11:18:39 +0200
commitd59157ea058b55b95f27675b33275ffe0f4c7bd6 (patch)
tree5bd8aae074365a816041cce7c5ab11cb003c7bee /docs/interop/vnc-ledstate-Pseudo-encoding.txt
parentinclude/exec/poison: Mark some CONFIG defines as poisoned, too (diff)
downloadqemu-d59157ea058b55b95f27675b33275ffe0f4c7bd6.tar.gz
qemu-d59157ea058b55b95f27675b33275ffe0f4c7bd6.tar.xz
qemu-d59157ea058b55b95f27675b33275ffe0f4c7bd6.zip
docs: create interop/ subdirectory
This is for the future interoperability & management guide. It includes the QAPI docs, including the automatically generated ones, other socket protocols (vhost-user, VNC), and the qcow2 file format. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'docs/interop/vnc-ledstate-Pseudo-encoding.txt')
-rw-r--r--docs/interop/vnc-ledstate-Pseudo-encoding.txt50
1 files changed, 50 insertions, 0 deletions
diff --git a/docs/interop/vnc-ledstate-Pseudo-encoding.txt b/docs/interop/vnc-ledstate-Pseudo-encoding.txt
new file mode 100644
index 0000000000..0f124f68b1
--- /dev/null
+++ b/docs/interop/vnc-ledstate-Pseudo-encoding.txt
@@ -0,0 +1,50 @@
+VNC LED state Pseudo-encoding
+=============================
+
+Introduction
+------------
+
+This document describes the Pseudo-encoding of LED state for RFB which
+is the protocol used in VNC as reference link below:
+
+http://tigervnc.svn.sourceforge.net/viewvc/tigervnc/rfbproto/rfbproto.rst?content-type=text/plain
+
+When accessing a guest by console through VNC, there might be mismatch
+between the lock keys notification LED on the computer running the VNC
+client session and the current status of the lock keys on the guest
+machine.
+
+To solve this problem it attempts to add LED state Pseudo-encoding
+extension to VNC protocol to deal with setting LED state.
+
+Pseudo-encoding
+---------------
+
+This Pseudo-encoding requested by client declares to server that it supports
+LED state extensions to the protocol.
+
+The Pseudo-encoding number for LED state defined as:
+
+======= ===============================================================
+Number Name
+======= ===============================================================
+-261 'LED state Pseudo-encoding'
+======= ===============================================================
+
+LED state Pseudo-encoding
+--------------------------
+
+The LED state Pseudo-encoding describes the encoding of LED state which
+consists of 3 bits, from left to right each bit represents the Caps, Num,
+and Scroll lock key respectively. '1' indicates that the LED should be
+on and '0' should be off.
+
+Some example encodings for it as following:
+
+======= ===============================================================
+Code Description
+======= ===============================================================
+100 CapsLock is on, NumLock and ScrollLock are off
+010 NumLock is on, CapsLock and ScrollLock are off
+111 CapsLock, NumLock and ScrollLock are on
+======= ===============================================================