From patchwork Wed Apr 24 10:12:30 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Lei Li X-Patchwork-Id: 239135 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from lists.gnu.org (lists.gnu.org [208.118.235.17]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 1BE1A2C00E8 for ; Wed, 24 Apr 2013 20:13:24 +1000 (EST) Received: from localhost ([::1]:36100 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUwhW-0006qq-7Q for incoming@patchwork.ozlabs.org; Wed, 24 Apr 2013 06:13:22 -0400 Received: from eggs.gnu.org ([208.118.235.92]:40913) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUwhA-0006mv-0U for qemu-devel@nongnu.org; Wed, 24 Apr 2013 06:13:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UUwh5-000619-38 for qemu-devel@nongnu.org; Wed, 24 Apr 2013 06:12:59 -0400 Received: from e23smtp04.au.ibm.com ([202.81.31.146]:59264) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUwh4-00060r-Hx for qemu-devel@nongnu.org; Wed, 24 Apr 2013 06:12:55 -0400 Received: from /spool/local by e23smtp04.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 24 Apr 2013 20:01:00 +1000 Received: from d23dlp02.au.ibm.com (202.81.31.213) by e23smtp04.au.ibm.com (202.81.31.210) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Wed, 24 Apr 2013 20:00:58 +1000 Received: from d23relay03.au.ibm.com (d23relay03.au.ibm.com [9.190.235.21]) by d23dlp02.au.ibm.com (Postfix) with ESMTP id 0F7592BB0059 for ; Wed, 24 Apr 2013 20:12:50 +1000 (EST) Received: from d23av01.au.ibm.com (d23av01.au.ibm.com [9.190.234.96]) by d23relay03.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r3OAChjY51904566 for ; Wed, 24 Apr 2013 20:12:43 +1000 Received: from d23av01.au.ibm.com (loopback [127.0.0.1]) by d23av01.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r3OACm2j005486 for ; Wed, 24 Apr 2013 20:12:48 +1000 Received: from localhost.localdomain ([9.77.178.91]) by d23av01.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r3OACcx1005080; Wed, 24 Apr 2013 20:12:47 +1000 From: Lei Li To: qemu-devel@nongnu.org Date: Wed, 24 Apr 2013 18:12:30 +0800 Message-Id: <1366798350-27068-4-git-send-email-lilei@linux.vnet.ibm.com> X-Mailer: git-send-email 1.7.7.6 In-Reply-To: <1366798350-27068-1-git-send-email-lilei@linux.vnet.ibm.com> References: <1366798350-27068-1-git-send-email-lilei@linux.vnet.ibm.com> X-Content-Scanned: Fidelis XPS MAILER x-cbid: 13042410-9264-0000-0000-0000039A21F3 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 202.81.31.146 Cc: lagarcia@br.ibm.com, aliguori@us.ibm.com, Lei Li Subject: [Qemu-devel] [PATCH 3/3] doc: document the Pseudo-encoding of LED state X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org Sender: qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org Signed-off-by: Lei Li --- docs/vnc-ledstate-Pseudo-encoding.txt | 40 +++++++++++++++++++++++++++++++++ 1 files changed, 40 insertions(+), 0 deletions(-) create mode 100644 docs/vnc-ledstate-Pseudo-encoding.txt diff --git a/docs/vnc-ledstate-Pseudo-encoding.txt b/docs/vnc-ledstate-Pseudo-encoding.txt new file mode 100644 index 0000000..0c312cf --- /dev/null +++ b/docs/vnc-ledstate-Pseudo-encoding.txt @@ -0,0 +1,40 @@ +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-enconding +-------------------------- + +The LED state Pseudo-encoding describes the encoding of LED state which +consists of 3 bits, each bit represents the Caps, Num, and Scroll lock +key respectively. '1' indicates that the LED should be on and '0' should +be off.