qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Fam Zheng <famz@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v7 4/6] ui: convert common input code to keycodemapdb
Date: Thu, 28 Sep 2017 13:25:47 -0500	[thread overview]
Message-ID: <3d611c0b-7920-2e3a-39c7-a3dff1b2b586@redhat.com> (raw)
In-Reply-To: <20170928120621.30288-5-berrange@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1787 bytes --]

On 09/28/2017 07:06 AM, Daniel P. Berrange wrote:
> Replace the number_to_qcode, qcode_to_number and linux_to_qcode
> tables with automatically generated tables.
> 
> Missing entries in linux_to_qcode now fixed:
> 
>   KEY_LINEFEED -> Q_KEY_CODE_LF
>   KEY_KPEQUAL -> Q_KEY_CODE_KP_EQUALS
>   KEY_COMPOSE -> Q_KEY_CODE_COMPOSE
>   KEY_AGAIN -> Q_KEY_CODE_AGAIN
>   KEY_PROPS -> Q_KEY_CODE_PROPS
>   KEY_UNDO -> Q_KEY_CODE_UNDO
>   KEY_FRONT -> Q_KEY_CODE_FRONT
>   KEY_COPY -> Q_KEY_CODE_COPY
>   KEY_OPEN -> Q_KEY_CODE_OPEN
>   KEY_PASTE -> Q_KEY_CODE_PASTE
>   KEY_CUT -> Q_KEY_CODE_CUT
>   KEY_HELP -> Q_KEY_CODE_HELP
>   KEY_MEDIA -> Q_KEY_CODE_MEDIASELECT
> 
> In additionsome fixes:

s/additionsome/addition, some/

> 
>  - KEY_PLAYPAUSE now maps to Q_KEY_CODE_AUDIOPLAY, instead of
>    KEY_PLAYCD. KEY_PLAYPAUSE is defined across almost all scancodes
>    sets, while KEY_PLAYCD only appears in AT set1, so the former is
>    a more useful mapping.
> 
> Missing entries in qcode_to_number now fixed:
> 
>   Q_KEY_CODE_AGAIN -> 0x85
>   Q_KEY_CODE_PROPS -> 0x86
>   Q_KEY_CODE_UNDO -> 0x87
>   Q_KEY_CODE_FRONT -> 0x8c
>   Q_KEY_CODE_COPY -> 0xf8
>   Q_KEY_CODE_OPEN -> 0x64
>   Q_KEY_CODE_PASTE -> 0x65
>   Q_KEY_CODE_CUT -> 0xbc
>   Q_KEY_CODE_LF -> 0x5b
>   Q_KEY_CODE_HELP -> 0xf5
>   Q_KEY_CODE_COMPOSE -> 0xdd
>   Q_KEY_CODE_KP_EQUALS -> 0x59
>   Q_KEY_CODE_MEDIASELECT -> 0xed
> 
> In addition some fixes:

Hmm - inconsistent with my suggestion above with regards to comma usage;
I think this is one scenario in English where you can get away without
the comma, even though I would use it.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

  reply	other threads:[~2017-09-28 18:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 12:06 [Qemu-devel] [PATCH v7 0/6] Initial support for keycodemapdb GIT submodule Daniel P. Berrange
2017-09-28 12:06 ` [Qemu-devel] [PATCH v7 1/6] build: automatically handle GIT submodule checkout for dtc Daniel P. Berrange
2017-09-28 17:58   ` Eric Blake
2017-09-29  9:08     ` Daniel P. Berrange
2017-09-28 17:59   ` Eric Blake
2017-09-29  9:09     ` Daniel P. Berrange
2017-09-28 12:06 ` [Qemu-devel] [PATCH v7 2/6] docker: don't rely on submodules existing in the main checkout Daniel P. Berrange
2017-09-28 18:03   ` Eric Blake
2017-09-29  9:14     ` Daniel P. Berrange
2017-10-02 12:55       ` Peter Maydell
2017-09-28 12:06 ` [Qemu-devel] [PATCH v7 3/6] ui: add keycodemapdb repository as a GIT submodule Daniel P. Berrange
2017-09-28 18:22   ` Eric Blake
2017-09-28 12:06 ` [Qemu-devel] [PATCH v7 4/6] ui: convert common input code to keycodemapdb Daniel P. Berrange
2017-09-28 18:25   ` Eric Blake [this message]
2017-09-28 12:06 ` [Qemu-devel] [PATCH v7 5/6] ui: convert key events to QKeyCodes immediately Daniel P. Berrange
2017-09-28 12:06 ` [Qemu-devel] [PATCH v7 6/6] ui: don't export qemu_input_event_new_key Daniel P. Berrange
2017-09-28 12:20 ` [Qemu-devel] [PATCH v7 0/6] Initial support for keycodemapdb GIT submodule no-reply

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=3d611c0b-7920-2e3a-39c7-a3dff1b2b586@redhat.com \
    --to=eblake@redhat.com \
    --cc=berrange@redhat.com \
    --cc=famz@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).