summaryrefslogtreecommitdiff
path: root/tcg-runtime.c
diff options
context:
space:
mode:
authorGerd Hoffmann <kraxel@redhat.com>2010-02-26 17:17:39 +0100
committerAnthony Liguori <aliguori@us.ibm.com>2010-03-09 08:47:27 -0600
commitde07af80aec0c8f4eb14fb1add28f2514d84a67e (patch)
tree8115121a288e7e5fefe74a1e5c95d702b1cc5948 /tcg-runtime.c
parent1504ab3c1624de0042b842d2a6834da85e53cb1a (diff)
downloadqemu-de07af80aec0c8f4eb14fb1add28f2514d84a67e.tar.gz
qemu-de07af80aec0c8f4eb14fb1add28f2514d84a67e.tar.bz2
qemu-de07af80aec0c8f4eb14fb1add28f2514d84a67e.zip
kbd keds: vnc
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. Also toggle the numlock and capslock states on keydown events (instead of keyup). Guests do the same. Signed-off-by: Gerd Hoffmann <kraxel@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'tcg-runtime.c')
0 files changed, 0 insertions, 0 deletions