qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>,
	Programmingkid <programmingkidx@gmail.com>
Cc: Scott Wood <scottwood@freescale.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	The OpenBIOS Mailinglist <openbios@openbios.org>,
	"qemu-ppc@nongnu.org list:PowerPC" <qemu-ppc@nongnu.org>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc]  Mac OS X on QEMU
Date: Wed, 10 Jul 2013 18:35:32 -0500	[thread overview]
Message-ID: <87y59eng3f.fsf@codemonkey.ws> (raw)
In-Reply-To: <AEF493B5-10CE-4631-BD13-2C33232D5D97@suse.de>

Alexander Graf <agraf@suse.de> writes:

> Am 10.07.2013 um 21:54 schrieb Programmingkid <programmingkidx@gmail.com>:
>
>> qemu-system-ppc -keyboard-layout-file ./keyboard-layout.txt 
>
> That's exactly what -k does today already, no?

No.  What we send to the guest is a scancode.  This literally
corresponds to "row 4, column 5".  With a good VNC client (like
gtk-vnc), the native GTK UI, or SDL, we're able to read these scan codes
directly from the keyboard and pass them to the guest.

So as long as you're using one of the above, you never have to think
about "-k".

However, a crappy VNC client (like realvnc) can only send symbolic key
symbols.  Literally "the D key".  However, QEMU has no idea what the
stickers are your physical keyboard.  So you have to tell it what the
symbolic key => scancode mapping is via the "-k" option.

Of course, we default to en-us which covers a lot of people.

Now, if for some goofy reason, you wanted to have rules that did:

map "row 4, column 5" => "row 6, column 9"

We would need a new interface for that.  But that's not something QEMU
should do IMHO.  I suspect this thread started because the OP is using a
crappy VNC client or a builtin UI that cannot pass through scan codes.

Regards,

Anthony Liguori

>
> Alex

  reply	other threads:[~2013-07-10 23:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2E45432C-6960-4E72-9F28-9848DF8A709A@gmail.com>
2013-07-04 14:45 ` [Qemu-devel] [Qemu-ppc] Mac OS X on QEMU Alexander Graf
2013-07-04 14:51   ` Stefan Hajnoczi
2013-07-04 14:58     ` Programmingkid
2013-07-09 17:32       ` Scott Wood
2013-07-10  3:36         ` Programmingkid
2013-07-10  4:10           ` [Qemu-devel] [OpenBIOS] " Tarl Neustaedter
2013-07-10 14:16             ` Programmingkid
2013-07-10 19:03           ` [Qemu-devel] " Scott Wood
2013-07-10 19:54             ` Programmingkid
2013-07-10 20:17               ` Scott Wood
2013-07-10 20:55                 ` Programmingkid
2013-07-10 21:12                   ` Scott Wood
2013-07-10 23:28                   ` Anthony Liguori
2013-07-11  1:43                     ` Programmingkid
2013-07-10 22:01               ` Alexander Graf
2013-07-10 23:35                 ` Anthony Liguori [this message]
2013-07-04 14:52   ` 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=87y59eng3f.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=agraf@suse.de \
    --cc=openbios@openbios.org \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=scottwood@freescale.com \
    --cc=stefanha@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).