From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:55723) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUMTc-0000Rk-9T for qemu-devel@nongnu.org; Mon, 22 Apr 2013 15:32:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UUMTb-0006CG-CB for qemu-devel@nongnu.org; Mon, 22 Apr 2013 15:32:36 -0400 Received: from e23smtp01.au.ibm.com ([202.81.31.143]:43805) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUMTa-0006C8-Ri for qemu-devel@nongnu.org; Mon, 22 Apr 2013 15:32:35 -0400 Received: from /spool/local by e23smtp01.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 23 Apr 2013 05:25:18 +1000 Received: from d23relay03.au.ibm.com (d23relay03.au.ibm.com [9.190.235.21]) by d23dlp01.au.ibm.com (Postfix) with ESMTP id 649FF2CE804A for ; Tue, 23 Apr 2013 05:32:29 +1000 (EST) Received: from d23av03.au.ibm.com (d23av03.au.ibm.com [9.190.234.97]) by d23relay03.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r3MJWLFg4522460 for ; Tue, 23 Apr 2013 05:32:23 +1000 Received: from d23av03.au.ibm.com (loopback [127.0.0.1]) by d23av03.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r3MJWRXe017791 for ; Tue, 23 Apr 2013 05:32:27 +1000 From: Anthony Liguori In-Reply-To: <516CF39B.3060904@redhat.com> References: <1365426454-6723-1-git-send-email-lilei@linux.vnet.ibm.com> <516BF534.3000909@redhat.com> <87wqs3g8ke.fsf@codemonkey.ws> <516C1F06.10909@redhat.com> <87vc7nlq55.fsf@codemonkey.ws> <516CF39B.3060904@redhat.com> Date: Mon, 22 Apr 2013 14:32:21 -0500 Message-ID: <87k3nul5tm.fsf@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [Qemu-devel] Support for VNC LED state extension proposal List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: lagarcia@br.ibm.com, Lei Li , qemu-devel@nongnu.org Gerd Hoffmann writes: > Hi, > >>> What is your vnc client? Does it support VNC_ENCODING_EXT_KEY_EVENT? >> >> It's uses gvnc as a protocol library and renders via fbdev. It reads >> keyboard events by putting /dev/tty into mediumraw mode and uses ext key >> events exclusively. It has no knowledge of the guest keymap. > > Neat. URL? We haven't published yet but I keep meaning too... It's really quite simple. > Does the linux kernel keep track of {caps,num}lock state (+leds) with > the keyboard in mediumraw mode? Nope. > Or does it expect the userspace app set the led state then? Yup. > No UI client (neither vnc nor spice) knows the guest keymap btw. Well, they do actually. gtk-vnc has key modifier tracking code. I assume gtk-spice does too. This code looks at the GdkEventKey::keysym which has gone through the host keymap. The assumption is that the host keymap == the guest keymap at least as far as modifiers are concerned. Take a look at key_event in vncdisplay.c in gtk-vnc. >> I believe VMware already has a VNC extension for passing LED state >> changes and I think having an open extension for this is a Good Thing. >> It's a pretty obvious missing piece in the VNC protocol. > > Anyone tried to bug vmware to open the specs for the existing > extension? I have in the past but that was many years ago at this point. Regards, Anthony Liguori > > cheers, > Gerd