qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 4/5] ui: add multimedia keys
Date: Wed, 26 Jul 2017 13:08:19 +0100	[thread overview]
Message-ID: <20170726120819.GH7620@redhat.com> (raw)
In-Reply-To: <85e9156c-1a11-4757-996d-877e40e316bc@redhat.com>

On Wed, Jul 26, 2017 at 07:02:48AM -0500, Eric Blake wrote:
> On 07/26/2017 06:56 AM, Gerd Hoffmann wrote:
> > Add multimedia keys to QKeyCodes and to the keymaps.
> > 
> > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> > ---
> >  ui/input-keymap.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
> >  qapi-schema.json  | 17 ++++++++++++++++-
> >  2 files changed, 60 insertions(+), 1 deletion(-)
> 
> > +++ b/qapi-schema.json
> > @@ -4843,6 +4843,16 @@
> >  # @henkan: since 2.9
> >  # @yen: since 2.9
> >  #
> > +# @sleep: since 2.10
> > +# @wake: since 2.10
> > +# @audio*: since 2.10
> > +# @volume*: since 2.10
> > +# @mediaselect: since 2.10
> > +# @mail: since 2.10
> > +# @calculator: since 2.10
> > +# @computer: since 2.10
> > +# @ac_*: since 2.10
> 
> Borderline between bug-fix and new feature (arguing that the bug is that
> we don't represent all keys).  Does this need to be 2.11 instead?

It is really fixing a bug introduced in the PS2 driver in 2.8.0.  It
roundtrips via QKeyCode now, so any key where there is an AT Set 1
scancode defined, but for which we lack a QKeyCode can't be sent to
guests since QEMU 2.8.0 onwards.

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 :|

  reply	other threads:[~2017-07-26 12:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26 11:56 [Qemu-devel] [PATCH 0/5] ui: keymap fixes for 2.10 Gerd Hoffmann
2017-07-26 11:56 ` [Qemu-devel] [PATCH 1/5] ui: add next and prior keysyms Gerd Hoffmann
2017-07-26 12:00   ` Eric Blake
2017-07-26 11:56 ` [Qemu-devel] [PATCH 2/5] ui: move qemu_input_linux_to_qcode() Gerd Hoffmann
2017-07-26 12:14   ` Eric Blake
2017-07-26 11:56 ` [Qemu-devel] [PATCH 3/5] ui: update keymaps Gerd Hoffmann
2017-07-26 12:25   ` Eric Blake
2017-07-26 11:56 ` [Qemu-devel] [PATCH 4/5] ui: add multimedia keys Gerd Hoffmann
2017-07-26 12:02   ` Eric Blake
2017-07-26 12:08     ` Daniel P. Berrange [this message]
2017-07-26 12:12       ` Eric Blake
2017-07-26 12:38         ` Gerd Hoffmann
2017-07-26 12:24   ` Eric Blake
2017-07-26 12:39     ` Gerd Hoffmann
2017-07-26 11:56 ` [Qemu-devel] [PATCH 5/5] ps2: enable " Gerd Hoffmann
2017-07-26 12:26   ` Eric Blake
2017-07-26 12:09 ` [Qemu-devel] [PATCH 0/5] ui: keymap fixes for 2.10 no-reply
2017-07-26 12:22   ` Eric Blake
2017-07-26 12:49     ` Gerd Hoffmann
2017-07-26 13:06       ` Eric Blake
2017-08-08  9:20     ` Markus Armbruster
2017-08-08 15:04       ` Eric Blake
2017-08-14  6:56         ` Markus Armbruster

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=20170726120819.GH7620@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=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).