From: Gerd Hoffmann <kraxel@redhat.com>
To: dvaleev@suse.de
Cc: Dinar Valeev <dvaleev@suse.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hw/input/hid.c Fix capslock hid code
Date: Thu, 22 Jan 2015 08:20:42 +0100 [thread overview]
Message-ID: <1421911242.9213.7.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <1421880521-7664-1-git-send-email-dvaleev@suse.de>
On Mi, 2015-01-21 at 23:48 +0100, dvaleev@suse.de wrote:
> From: Dinar Valeev <dvaleev@suse.com>
>
> When ever USB keyboard is used, e.g. '-usbdevice keyboard' pressing
> caps lock key send 0x32 hid code, which is treated as backslash.
> Instead it should be 0x39 code. This affects sending uppercase keys,
> as they typed whith caps lock active.
>
> While on x86 this can be workarounded by using ps/2 protocol. On
> Power it is crusial as we don't have anything else than USB.
>
> This is fixes guest automation tasts over vnc.
That probably happens because your test automation vnc client sends
uppercase letters without also sending shift-down/up events. The qemu
vnc server logic which is supposed to sync up capslock state between
guest and host thinks capslock is pressed on the host then and injects
some synthetic capslock key events.
Just say'ing FYI, that doesn't render the fix invalid, but you may have
wondered why you are not seeing this with a normal vnc client ;)
Added to input queue.
thanks,
Gerd
next prev parent reply other threads:[~2015-01-22 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 22:48 [Qemu-devel] [PATCH] hw/input/hid.c Fix capslock hid code dvaleev
2015-01-22 7:20 ` Gerd Hoffmann [this message]
2015-01-22 7:59 ` Dinar Valeev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1421911242.9213.7.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=dvaleev@suse.com \
--cc=dvaleev@suse.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).