From: andrzej zaborowski <balrogg@gmail.com>
To: qemu-devel@nongnu.org, "Carlos A. M. dos Santos" <unixmania@gmail.com>
Subject: Re: [Qemu-devel] unknown keycodes `xfree86(abnt2)_aliases(qwerty)'
Date: Mon, 13 Apr 2009 13:37:32 +0200 [thread overview]
Message-ID: <fb249edb0904130437idd1f030jdce7897816b2ce31@mail.gmail.com> (raw)
In-Reply-To: <e71790db0904121902p60b7d439oce535b8cc9b5b303@mail.gmail.com>
2009/4/13 Carlos A. M. dos Santos <unixmania@gmail.com>:
> Hello,
>
> Each time I start qemu I see this message:
>
> unknown keycodes `xfree86(abnt2)_aliases(qwerty)', please report
> to qemu-devel@nongnu.org
I changed sdl.c to accept all strings starting with xfree86 and evdev
rather than xfree86_ and evdev_ because we're only interested in
whether the keymap used is an evdev or an X one. With my Xorg 1.5 I
had a similar warning and someone else using an evdev driver also had
a similar one.
Thanks for report
prev parent reply other threads:[~2009-04-13 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 2:02 [Qemu-devel] unknown keycodes `xfree86(abnt2)_aliases(qwerty)' Carlos A. M. dos Santos
2009-04-13 11:37 ` andrzej zaborowski [this message]
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=fb249edb0904130437idd1f030jdce7897816b2ce31@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=unixmania@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).