From: Peter Maydell <peter.maydell@linaro.org>
To: jakub@jermar.eu
Cc: qemu-devel@nongnu.org, vineethrp@gmail.com
Subject: Re: [Qemu-devel] [arm] Integrator/CP keyboard layout
Date: Tue, 22 Mar 2011 15:50:32 +0000 [thread overview]
Message-ID: <AANLkTin8BiCv+PMCYpYxdjZ5apm_zW9RtHZPn4ifdCBT@mail.gmail.com> (raw)
In-Reply-To: <20110322161904.804857t9z0pbczk0@mail.hosting123.cz>
On 22 March 2011 15:19, <jakub@jermar.eu> wrote:
> Quoting Peter Maydell <peter.maydell@linaro.org>:
>> On 21 March 2011 23:03, Jakub Jermar <jakub@jermar.eu> wrote:
>>> I noticed that the layout of the PL050 keyboard used on Integrator/CP
>>> incompatibly changed sometime between Qemu 0.10.5 and Qemu 0.11.1. The
>>> current layout used in Qemu's model of Integrator/CP is the standard PC
>>> layout. What puzzles me is whether this was a fix or a regression. Does
>>> anybody know what was the motivation for that change?
>>
>> The PL050 is just a PS/2 keyboard (or mouse) interface -- so
>> it doesn't have any control over the keyboard layout (either
>> in hardware or in qemu's model); I guess you're seeing the
>> effects of a non-ARM-specific change to PS/2 keyboard handling.
> I would tend to think that there is only one correct set of key codes
> that the keyboard on Integrator/CP may generate.
Why do you think this? The keyboard isn't built in to the hardware,
so the set of keycodes you get depends on the keyboard, not the
Integrator/CP. (Conversely, you should get the same set of keycodes
for an Integrator/CP as you would for a PC model, so if there was
a difference in 0.10.5 this is a progression, not a regression.)
-- PMM
next prev parent reply other threads:[~2011-03-22 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 23:03 [Qemu-devel] [arm] Integrator/CP keyboard layout Jakub Jermar
2011-03-22 10:24 ` Peter Maydell
2011-03-22 15:19 ` jakub
2011-03-22 15:50 ` Peter Maydell [this message]
2011-03-22 16:44 ` jakub
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=AANLkTin8BiCv+PMCYpYxdjZ5apm_zW9RtHZPn4ifdCBT@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=jakub@jermar.eu \
--cc=qemu-devel@nongnu.org \
--cc=vineethrp@gmail.com \
/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).