From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PATCH 0/3] Fix qemu keymaps, part one
Date: Mon, 24 Jul 2017 16:01:14 +0200 [thread overview]
Message-ID: <20170724140117.27651-1-kraxel@redhat.com> (raw)
qemu carries a bunch of reverse keymaps in pc-bios/keymaps/, to map
keysyms it receives from vnc clients back to keycodes. These keymaps
seem to be buggy and incomplete at times. So, to tackle the issue once
for all, I've written a tool to generate those maps from xkb keyboard
layout data using libxkbcommon.
This patch series only adds the tool, it doesn't touch the maps in
pc-bios/keymaps/ yet. I want some testing feedback first ...
How to test:
(1) generate a map: "qemu-keymap -f testmap -l $layout"
(2) use the map: "qemu -vnc $display -k testmap"
Gerd Hoffmann (3):
keysym: add next and prior
ui: move qemu_input_linux_to_qcode()
Add qemu-keymap tool.
configure | 23 +++++
Makefile | 5 ++
include/ui/input.h | 1 +
ui/curses_keys.h | 2 +
ui/vnc_keysym.h | 2 +
qemu-keymap.c | 243 +++++++++++++++++++++++++++++++++++++++++++++++++++++
ui/input-keymap.c | 115 +++++++++++++++++++++++++
ui/input-linux.c | 113 -------------------------
8 files changed, 391 insertions(+), 113 deletions(-)
create mode 100644 qemu-keymap.c
--
2.9.3
next reply other threads:[~2017-07-24 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 14:01 Gerd Hoffmann [this message]
2017-07-24 14:01 ` [Qemu-devel] [PATCH 1/3] keysym: add next and prior Gerd Hoffmann
2017-07-24 14:01 ` [Qemu-devel] [PATCH 2/3] ui: move qemu_input_linux_to_qcode() Gerd Hoffmann
2017-07-24 14:01 ` [Qemu-devel] [PATCH 3/3] Add qemu-keymap tool Gerd Hoffmann
2017-07-24 14:18 ` [Qemu-devel] [PATCH 0/3] Fix qemu keymaps, part one Daniel P. Berrange
2017-07-24 14:23 ` Daniel P. Berrange
2017-07-24 14:29 ` Gerd Hoffmann
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=20170724140117.27651-1-kraxel@redhat.com \
--to=kraxel@redhat.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).