From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NlY6i-0003p2-OG
	for qemu-devel@nongnu.org; Sat, 27 Feb 2010 20:38:08 -0500
Received: from [199.232.76.173] (port=60215 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NlY6i-0003oh-CP
	for qemu-devel@nongnu.org; Sat, 27 Feb 2010 20:38:08 -0500
Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim
	4.60) (envelope-from <paul@codesourcery.com>) id 1NlY6h-0007RE-OZ
	for qemu-devel@nongnu.org; Sat, 27 Feb 2010 20:38:08 -0500
Received: from mx20.gnu.org ([199.232.41.8]:56729)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <paul@codesourcery.com>)
	id 1NlY6h-0007R2-GP
	for qemu-devel@nongnu.org; Sat, 27 Feb 2010 20:38:07 -0500
Received: from mail.codesourcery.com ([38.113.113.100])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1NlY6g-0004WZ-NG
	for qemu-devel@nongnu.org; Sat, 27 Feb 2010 20:38:07 -0500
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH 4/4] kbd keds: vnc
Date: Sun, 28 Feb 2010 01:38:04 +0000
References: <1267087161-15204-1-git-send-email-kraxel@redhat.com>
	<1267087161-15204-5-git-send-email-kraxel@redhat.com>
In-Reply-To: <1267087161-15204-5-git-send-email-kraxel@redhat.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201002280138.04634.paul@codesourcery.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>

> Use led status notification support in vnc.
> 
> The qemu vnc server keeps track of the capslock and numlock states based
> on the key presses it receives from the vnc client.  But this fails in
> case the guests idea of the capslock and numlock state changes for other
> reasons.  One case is guest reboot (+ keyboard reset).  Another case are
> more recent windows versions which reset capslock state before
> presenting the login screen.
> 
> Usually guests use the keyboard leds to signal the capslock and numlock
> state to the user, so we can use this to better keep track of capslock
> and numlock state in the qemu vnc server.

Isn't this going to break horribly when my guest starts flashing the capslock 
light in response to network traffic?

Paul