From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL 00/10] input layer rework continued
Date: Fri, 16 May 2014 08:47:21 +0200 [thread overview]
Message-ID: <1400222851-6725-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
Update for the input layer. Add keycode mapping helpers,
start switching over devices to the new input api, fixes.
please pull,
Gerd
The following changes since commit 1a381811b495651ddfc2b50d7c8cfaaf375816b0:
Merge remote-tracking branch 'remotes/rth/tags/pull-tcg-s390-20140515' into staging (2014-05-15 18:56:08 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/pull-input-8
for you to fetch changes up to 59e7a130054b55fe15cdfdebf284332b04d990ef:
input: sparc32 kbd: claim en-us layout (2014-05-16 08:30:12 +0200)
----------------------------------------------------------------
Input code update:
- add keycode mapping helpers to core.
- start switching devices to new input api.
- misc bugfixes.
----------------------------------------------------------------
Gerd Hoffmann (9):
input: key mapping helpers
input: add qemu_input_handler_deactivate
input: use KeyValue directly in sendkey monitor command
input: switch ps/2 kbd to new input api
input: switch ps/2 mouse to new input api
input: switch sparc32 kbd to new input api
input: remove sparc keymap hack
input: sparc32 kbd: fix some key mappings
input: sparc32 kbd: claim en-us layout
Gonglei (1):
ps2: set ps/2 output buffer size as the same as kernel
hw/char/escc.c | 233 +++++++++++++++++++++++++++++++++++++++--------------
hw/input/ps2.c | 166 +++++++++++++++++++++++++++++++++-----
include/ui/input.h | 5 ++
trace-events | 4 +-
ui/Makefile.objs | 3 +-
ui/input-keymap.c | 191 +++++++++++++++++++++++++++++++++++++++++++
ui/input-legacy.c | 226 +++++++--------------------------------------------
ui/input.c | 7 ++
8 files changed, 553 insertions(+), 282 deletions(-)
create mode 100644 ui/input-keymap.c
next reply other threads:[~2014-05-16 6:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 6:47 Gerd Hoffmann [this message]
2014-05-16 6:47 ` [Qemu-devel] [PULL 01/10] ps2: set ps/2 output buffer size as the same as kernel Gerd Hoffmann
2014-05-16 6:47 ` [Qemu-devel] [PULL 02/10] input: key mapping helpers Gerd Hoffmann
2014-05-16 6:47 ` [Qemu-devel] [PULL 03/10] input: add qemu_input_handler_deactivate Gerd Hoffmann
2014-05-16 6:47 ` [Qemu-devel] [PULL 04/10] input: use KeyValue directly in sendkey monitor command Gerd Hoffmann
2014-05-16 6:47 ` [Qemu-devel] [PULL 05/10] input: switch ps/2 kbd to new input api Gerd Hoffmann
2014-05-16 6:47 ` [Qemu-devel] [PULL 06/10] input: switch ps/2 mouse " Gerd Hoffmann
2014-05-16 6:47 ` [Qemu-devel] [PULL 07/10] input: switch sparc32 kbd " Gerd Hoffmann
2014-05-16 6:47 ` [Qemu-devel] [PULL 08/10] input: remove sparc keymap hack Gerd Hoffmann
2014-05-16 6:47 ` [Qemu-devel] [PULL 09/10] input: sparc32 kbd: fix some key mappings Gerd Hoffmann
2014-05-16 6:47 ` [Qemu-devel] [PULL 10/10] input: sparc32 kbd: claim en-us layout Gerd Hoffmann
2014-05-18 16:14 ` [Qemu-devel] [PULL 00/10] input layer rework continued Olivier Danet
2014-05-19 13:09 ` Peter Maydell
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=1400222851-6725-1-git-send-email-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).