From: Peter Maydell <peter.maydell@linaro.org>
To: Programmingkid <programmingkidx@gmail.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v4 4/4] hw/input/adb.c: implement QKeyCode support
Date: Tue, 15 Mar 2016 09:22:56 +0000 [thread overview]
Message-ID: <CAFEAcA-YoJpW9N3bBFBvWjeS3uYhP9+gFbuvf7F1mt_MH=Ez9g@mail.gmail.com> (raw)
In-Reply-To: <77582ECD-0206-4FD9-AE2C-3B31E78FA44F@gmail.com>
On 14 March 2016 at 23:06, Programmingkid <programmingkidx@gmail.com> wrote:
> On Mar 13, 2016, at 11:40 AM, Peter Maydell wrote:
>> Also, you need to handle the power-key key-release
>> scancode; as far as I can tell (by looking for info via
>> google about the ADB protocol) power-key-down is
>> 0x7f 0x7f, and power-key-up is 0xff 0xff. (This is
>> kind of weird and suggests we should just take option
>> (a) and special case the power key completely.)
>
> The power-key-up (break) keycode is 0xff 0xff? Could you send me your
> source for this information?
https://developer.apple.com/legacy/library/technotes/hw/hw_01.html
(section "Apple Keyboard Protocol").
Power-key is a weird one both for key-up and key-down.
thanks
-- PMM
next prev parent reply other threads:[~2016-03-15 9:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 2:32 [Qemu-devel] [PATCH v4 4/4] hw/input/adb.c: implement QKeyCode support Programmingkid
2016-03-12 3:30 ` Peter Maydell
2016-03-12 4:27 ` Programmingkid
2016-03-13 16:00 ` Peter Maydell
2016-03-12 5:40 ` Programmingkid
2016-03-13 15:40 ` Peter Maydell
2016-03-13 16:39 ` Programmingkid
2016-03-13 16:42 ` Peter Maydell
2016-03-14 23:06 ` Programmingkid
2016-03-14 23:10 ` M A
2016-03-15 9:22 ` Peter Maydell [this message]
2016-03-15 15:24 ` Programmingkid
2016-03-15 15:34 ` Peter Maydell
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='CAFEAcA-YoJpW9N3bBFBvWjeS3uYhP9+gFbuvf7F1mt_MH=Ez9g@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=kraxel@redhat.com \
--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 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.