From patchwork Fri Apr 19 18:11:52 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Lei Li X-Patchwork-Id: 238086 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 A8B522C0230 for ; Sat, 20 Apr 2013 04:14:14 +1000 (EST) Received: from localhost ([::1]:60354 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UTFp6-0006hB-RI for incoming@patchwork.ozlabs.org; Fri, 19 Apr 2013 14:14:12 -0400 Received: from eggs.gnu.org ([208.118.235.92]:40003) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UTFne-00056R-MR for qemu-devel@nongnu.org; Fri, 19 Apr 2013 14:12:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UTFnd-0007qc-NO for qemu-devel@nongnu.org; Fri, 19 Apr 2013 14:12:42 -0400 Received: from e23smtp08.au.ibm.com ([202.81.31.141]:37211) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UTFnd-0007qP-5i for qemu-devel@nongnu.org; Fri, 19 Apr 2013 14:12:41 -0400 Received: from /spool/local by e23smtp08.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Sat, 20 Apr 2013 04:10:24 +1000 Received: from d23dlp03.au.ibm.com (202.81.31.214) by e23smtp08.au.ibm.com (202.81.31.205) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Sat, 20 Apr 2013 04:10:22 +1000 Received: from d23relay05.au.ibm.com (d23relay05.au.ibm.com [9.190.235.152]) by d23dlp03.au.ibm.com (Postfix) with ESMTP id E1C77357804A for ; Sat, 20 Apr 2013 04:12:35 +1000 (EST) Received: from d23av04.au.ibm.com (d23av04.au.ibm.com [9.190.235.139]) by d23relay05.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r3JHwRUZ5177702 for ; Sat, 20 Apr 2013 03:58:27 +1000 Received: from d23av04.au.ibm.com (loopback [127.0.0.1]) by d23av04.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r3JIC5UZ001008 for ; Sat, 20 Apr 2013 04:12:05 +1000 Received: from localhost.localdomain ([9.125.28.99]) by d23av04.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r3JIBuUw000911; Sat, 20 Apr 2013 04:12:03 +1000 From: Lei Li To: qemu-devel@nongnu.org Date: Sat, 20 Apr 2013 02:11:52 +0800 Message-Id: <1366395112-31581-4-git-send-email-lilei@linux.vnet.ibm.com> X-Mailer: git-send-email 1.7.7.6 In-Reply-To: <1366395112-31581-1-git-send-email-lilei@linux.vnet.ibm.com> References: <1366395112-31581-1-git-send-email-lilei@linux.vnet.ibm.com> x-cbid: 13041918-5140-0000-0000-000003104161 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 202.81.31.141 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 | 33 +++++++++++++++++++++++++++++++++ 1 files changed, 33 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..3f3fd15 --- /dev/null +++ b/docs/vnc-ledstate-Pseudo-encoding.txt @@ -0,0 +1,33 @@ +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. + +Example +------- + +The example psuedo-encodings for LED state defined as following: + +======= =============================================================== +Code Description +======= =============================================================== +100 CapsLock is set +010 NumLock is set +001 ScrollLock is set +110 CapsLock and NumLock are set +111 CapsLock, NumLock and ScrollLock are set +======= ===============================================================