From: Oliver Gerlich <olig9@gmx.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ESC key problems & keyboard problems
Date: Wed, 09 Mar 2005 12:16:22 +0100 [thread overview]
Message-ID: <422EDB06.5000604@gmx.de> (raw)
In-Reply-To: <200503080151.16759.prdcomp@uol.com.br>
There was a fix in CVS some days ago which made ESC available with
keymaps. If you get errors on your console when pressing ESC, you should
try a newer CVS snapshot.
Oliver Gerlich
Paulo R. Dallan schrieb:
> Hi!
>
> I've been using qemu/kqemu in a linux host - very nice work folks,
> congratulations.
>
> I'm just having a little keyboard problem. Unfortunately, if I don't choose a
> keyboard layout ("-k pt-br"), the key "/" and "?" is not recognized either in
> Linux or Windows (its a Brazilian ABNT2 keyboard).
>
> However, when I choose a keyboard map ("-k en-us", for example), the ESC key
> does not work.
>
> Is anyone having the same problem?
>
> PS: Just a side note, some time ago, there was a similar little bug in kbd,
> after compiling dri - open source video acceleration drivers - from sources,
> by which certain keys - especially this "/" and "?" key was not recognized; I
> noticed the problem after installing a dri video driver from source, and
> solved it through the quick & dirty solution I described here:
>
> http://sourceforge.net/mailarchive/message.php?msg_id=7263141
>
> More comments about it here:
>
> http://sourceforge.net/mailarchive/message.php?msg_id=7264988
>
> and here:
>
> http://sourceforge.net/mailarchive/message.php?msg_id=7289423
>
> Considering that according to information contained in qemu source files
> related to the keyboard layouts, same are based on kbd, and as it seems some
> information may have come from Red Hat 7 or 9.0
> (http://fabrice.bellard.free.fr/qemu/qemu-doc.html#TOC42), which uses xfree86
> (which dri also used at the time), there may be some connection between the
> problems and the solution to this little annoyance in qemu may be related
> (not sure how the keymaps are used in qemu though)...
>
> Another note is that there was no such problem after dri moved to xorg (and
> its kbd version). Don't know if this has been solved in later xfree86
> editions.
>
> Anyway, best regards and congratulations for the excellent work!
>
> Paulo
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
>
next prev parent reply other threads:[~2005-03-09 11:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 20:55 [Qemu-devel] gentoo disk image for QEmu Jérôme Bouat
2005-03-07 21:26 ` Magnus Damm
2005-03-08 1:51 ` [Qemu-devel] ESC key problems & keyboard problems Paulo R. Dallan
2005-03-09 11:16 ` Oliver Gerlich [this message]
2005-03-09 18:44 ` Paulo R. Dallan
2005-03-10 22:52 ` [Qemu-devel] Still some keyboard problems (was: ESC key problems & keyboard problems) Paulo R. Dallan
2005-03-12 21:33 ` [Qemu-devel] Still some keyboard problems Oliver Gerlich
2005-03-12 9:55 ` [Qemu-devel] gentoo disk image for QEmu Jérôme Bouat
2005-03-12 10:31 ` Magnus Damm
2005-04-01 13:05 ` [Qemu-devel] x86 emulated hardware : which make.conf options ? Jérôme Bouat
2005-04-01 13:14 ` Karel Gardas
2005-04-01 17:26 ` Natalia Portillo
2005-04-01 18:04 ` Paul Brook
2005-04-02 16:38 ` Natalia Portillo
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=422EDB06.5000604@gmx.de \
--to=olig9@gmx.de \
--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).