qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL 00/10] input: add event routing and multiseat support.
Date: Mon, 26 May 2014 09:51:16 +0200	[thread overview]
Message-ID: <1401090686-1095-1-git-send-email-kraxel@redhat.com> (raw)

  Hi,

Input layer continued:  Adding input routing for multiseat.
Also has some bugfixes.

please pull,
  Gerd

The following changes since commit 178ac111bca16c08a79b2609ebdc75197bea976a:

  Merge remote-tracking branch 'remotes/qmp-unstable/queue/qmp' into staging (2014-05-22 19:04:49 +0100)

are available in the git repository at:


  git://git.kraxel.org/qemu tags/pull-input-9

for you to fetch changes up to 8977bd111f62035b675d41c432eb8b6bf6b86b0f:

  docs: add multiseat.txt (2014-05-26 08:42:43 +0200)

----------------------------------------------------------------
input: add event routing and multiseat support.
input: misc bugfixes and minor improvements.

----------------------------------------------------------------
Andrew Oates (1):
      input (curses): mask keycodes to remove modifier bits

Gerd Hoffmann (9):
      input: add qemu_input_key_number_to_qcode
      input: add name to input_event_key_number
      input: keymap: add meta keys
      input: switch hid keyboard to new input layer api.
      input: switch hid mouse and tablet to the new input layer api.
      input: bind devices and input routing
      sdl: pass key event source to input layer
      usb: add input routing support for tablet and keyboard
      docs: add multiseat.txt

 docs/multiseat.txt     |  76 +++++++++++++++++
 hw/input/hid.c         | 220 ++++++++++++++++++++++++++++++++-----------------
 hw/usb/dev-hid.c       |  13 +++
 include/hw/input/hid.h |   4 +-
 include/ui/input.h     |   4 +
 trace-events           |   2 +-
 ui/curses.c            |   4 +-
 ui/input-keymap.c      |  13 ++-
 ui/input.c             |  49 +++++++++--
 ui/sdl2.c              |  21 +++--
 10 files changed, 308 insertions(+), 98 deletions(-)
 create mode 100644 docs/multiseat.txt

             reply	other threads:[~2014-05-26  7:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26  7:51 Gerd Hoffmann [this message]
2014-05-26  7:51 ` [Qemu-devel] [PULL 01/10] input (curses): mask keycodes to remove modifier bits Gerd Hoffmann
2014-05-26  7:51 ` [Qemu-devel] [PULL 02/10] input: add qemu_input_key_number_to_qcode Gerd Hoffmann
2014-05-26  7:51 ` [Qemu-devel] [PULL 03/10] input: add name to input_event_key_number Gerd Hoffmann
2014-05-26  7:51 ` [Qemu-devel] [PULL 04/10] input: keymap: add meta keys Gerd Hoffmann
2014-05-26  7:51 ` [Qemu-devel] [PULL 05/10] input: switch hid keyboard to new input layer api Gerd Hoffmann
2014-05-26  7:51 ` [Qemu-devel] [PULL 06/10] input: switch hid mouse and tablet to the " Gerd Hoffmann
2014-05-26  7:51 ` [Qemu-devel] [PULL 07/10] input: bind devices and input routing Gerd Hoffmann
2014-05-26  7:51 ` [Qemu-devel] [PULL 08/10] sdl: pass key event source to input layer Gerd Hoffmann
2014-05-26  7:51 ` [Qemu-devel] [PULL 09/10] usb: add input routing support for tablet and keyboard Gerd Hoffmann
2014-05-26  7:51 ` [Qemu-devel] [PULL 10/10] docs: add multiseat.txt 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=1401090686-1095-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).