From: "Daniel P. Berrange" <berrange@redhat.com>
To: Miika S <miika9764@gmail.com>
Cc: qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] Key code conflict in keycodemapdb
Date: Fri, 15 Dec 2017 13:57:38 +0000 [thread overview]
Message-ID: <20171215135738.GF11724@redhat.com> (raw)
In-Reply-To: <CABMrAhLV6LLwBR70-P4EnekWHKD4AkaatzxQwuxtOnNYQ3MEqQ@mail.gmail.com>
On Fri, Dec 15, 2017 at 03:51:19PM +0200, Miika S wrote:
> Hi
>
> I tried to add JIS keyboard support to virtio-input-hid but ran
> into a problem with keys that have the "Linux Name" KEY_ISO and
> KEY_KATAKANAHIRAGANA. The problem appears to be that they have
> the same "AT set1 keycode" 0x70. I worked around it by removing
> KEY_ISO from keycodemapdb and got the keys working, but that
> doesn't work for the rest of QEMU. Is it intended that the keys
> have the same "AT set1 keycode"?
It is probably a misake
> @@ -246,7 +246,6 @@
> KEY_STOPCD,166,,,0xe024,0xe03b,0x98,233,VK_MEDIA_STOP,0xb2,,,,,MediaStop,I174,au
> KEY_RECORD,167,,,0xe031,,0x9e,,,,,,,,,I175,,,
> KEY_REWIND,168,,,0xe018,,0x9f,,,,,,,,,I176,,,
> KEY_PHONE,169,,,0x63,,,,,,,,,,,I177,,,
> -KEY_ISO,170,ISO_Section,0xa,0x70,,,,,,,,,,,I178,,,
Instead of deleteing this line entirely, the right fix is probably to just
blank out the 0x70 value here.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-12-15 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 13:51 [Qemu-devel] Key code conflict in keycodemapdb Miika S
2017-12-15 13:57 ` Daniel P. Berrange [this message]
2017-12-15 20:03 ` Miika S
2017-12-18 10:57 ` Daniel P. Berrange
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=20171215135738.GF11724@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=miika9764@gmail.com \
--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).