qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Eric Blake <eblake@redhat.com>,
	"qemu-devel@nongnu.org qemu-devel" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 1/2] Add more function keys to QEMU
Date: Mon, 31 Jul 2017 14:10:10 +0100	[thread overview]
Message-ID: <20170731131010.GB21310@redhat.com> (raw)
In-Reply-To: <421095EC-3086-46A4-AA1E-653831EA746D@gmail.com>

On Mon, Jul 31, 2017 at 08:46:56AM -0400, Programmingkid wrote:
> 
> > On Jul 31, 2017, at 5:46 AM, Daniel P. Berrange <berrange@redhat.com> wrote:
> > 
> > On Sun, Jul 30, 2017 at 04:29:27PM -0400, Programmingkid wrote:
> >> There are now keyboards that have 19 function keys. This patch extends QEMU so these function keys can be used.
> >> 
> >> Signed-off-by: John Arbuckle <programmingkidx@gmail.com>
> >> ---
> >> qapi-schema.json  | 12 +++++++++++-
> >> ui/input-keymap.c |  9 +++++++++
> >> 2 files changed, 20 insertions(+), 1 deletion(-)
> >> 
> >> diff --git a/qapi-schema.json b/qapi-schema.json
> >> index c96f0a2..f1c989b 100644
> >> --- a/qapi-schema.json
> >> +++ b/qapi-schema.json
> >> @@ -4862,6 +4862,15 @@
> >> # @ac_refresh: since 2.10
> >> # @ac_bookmarks: since 2.10
> >> # altgr, altgr_r: dropped in 2.10
> >> +# @f16: since 2.11
> >> +# @f17: since 2.11
> >> +# @f18: since 2.11
> >> +# @f19: since 2.11
> >> +# @f20: since 2.11
> >> +# @f21: since 2.11
> >> +# @f22: since 2.11
> >> +# @f23: since 2.11
> >> +# @f24: since 2.11
> >> #
> >> # Since: 1.3.0
> >> #
> >> @@ -4888,7 +4897,8 @@
> >>             'audionext', 'audioprev', 'audiostop', 'audioplay', 'audiomute',
> >>             'volumeup', 'volumedown', 'mediaselect',
> >>             'mail', 'calculator', 'computer',
> >> -            'ac_home', 'ac_back', 'ac_forward', 'ac_refresh', 'ac_bookmarks' ] }
> >> +            'ac_home', 'ac_back', 'ac_forward', 'ac_refresh', 'ac_bookmarks',
> >> +            'f16', 'f17', 'f18', 'f19', 'f20', 'f21', 'f22', 'f23', 'f24'] }
> >> 
> >> ##
> >> # @KeyValue:
> > 
> > This bit looks fine.
> > 
> >> diff --git a/ui/input-keymap.c b/ui/input-keymap.c
> >> index cf979c2..c0413e1 100644
> >> --- a/ui/input-keymap.c
> >> +++ b/ui/input-keymap.c
> >> @@ -251,6 +251,15 @@ static const int qcode_to_number[] = {
> >> 
> >>     [Q_KEY_CODE_F11] = 0x57,
> >>     [Q_KEY_CODE_F12] = 0x58,
> >> +    [Q_KEY_CODE_F16] = 0x59,
> >> +    [Q_KEY_CODE_F17] = 0x5a,
> >> +    [Q_KEY_CODE_F18] = 0x5b,
> >> +    [Q_KEY_CODE_F19] = 0x5c,
> >> +    [Q_KEY_CODE_F20] = 0x5d,
> >> +    [Q_KEY_CODE_F21] = 0x5e,
> >> +    [Q_KEY_CODE_F22] = 0x5f,
> >> +    [Q_KEY_CODE_F23] = 0x60,
> >> +    [Q_KEY_CODE_F24] = 0x61,
> > 
> > You've got a gap there F13, F14, F15 were all missing (pre-existing bug in
> > QEMU), so you can't carry on just incrementing after F12.
> 
> Actually F13, F14,and F15 are called Q_KEY_CODE_PRINT, Q_KEY_CODE_SCROLL_LOCK,
> and Q_KEY_CODE_PAUSE respectively.

Huh. That's not right. Print/Scroll/Pause are completely separate to F13/14/15


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-31 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-30 20:29 [Qemu-devel] [PATCH v2 1/2] Add more function keys to QEMU Programmingkid
2017-07-31  9:46 ` Daniel P. Berrange
2017-07-31 12:46   ` Programmingkid
2017-07-31 13:10     ` Daniel P. Berrange [this message]
2017-07-31 14:52       ` Programmingkid
2017-07-31 15:06         ` Daniel P. Berrange
2017-07-31 15:12           ` Programmingkid

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=20170731131010.GB21310@redhat.com \
    --to=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=programmingkidx@gmail.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).