All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] input: introduce keyboard handler list
Date: Thu, 07 Mar 2013 16:36:03 +0100	[thread overview]
Message-ID: <5138B3E3.9080309@redhat.com> (raw)
In-Reply-To: <87a9qfb7vu.fsf@blackfin.pond.sub.org>

  Hi,

> For mice, we have a monitor command mouse_set to select the active one.
> Useful for keyboards, too?  I dimly recall somebody trying something
> like that in the past.

Don't feel like doing that now.

First, isn't important enough IMHO.

Second, I'm busy cleaning up console + display code.  With this done it
should be easy to have proper multihead support (not the somewhat
hackish way we do it with spice now, where the qemu console / display
code is completely bypassed by secondary qxl cards).  And once we have
that we'll probably wanna have input *routing* instead of input
*selection*, i.e. input from this ui window goes to that virtual
mouse/keyboard, so we can emulate multiseat setups ...

cheers,
  Gerd

  reply	other threads:[~2013-03-07 15:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1362037315-26896-1-git-send-email-kraxel@redhat.com>
     [not found] ` <1362037315-26896-3-git-send-email-kraxel@redhat.com>
2013-03-07 14:29   ` [Qemu-devel] [PATCH 2/2] input: introduce keyboard handler list Markus Armbruster
2013-03-07 15:36     ` Gerd Hoffmann [this message]
2013-03-07 16:10       ` Markus Armbruster
     [not found] ` <1362037315-26896-2-git-send-email-kraxel@redhat.com>
2013-03-07 14:29   ` [Qemu-devel] [PATCH 1/2] input: make QEMUPutLEDEntry + QEMUPutMouseEntry private Markus Armbruster
2013-04-24 10:08 [Qemu-devel] [RESEND PATCH 0/2] input: kbd handler list Gerd Hoffmann
2013-04-24 10:08 ` [Qemu-devel] [PATCH 2/2] input: introduce keyboard " 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=5138B3E3.9080309@redhat.com \
    --to=kraxel@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=armbru@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.