From: "Jim C. Brown" <jma5@umd.edu>
To: Marcus Blomenkamp <mblomenkamp@web.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Keyboard/monitor problems when running not under X
Date: Fri, 4 Nov 2005 11:25:29 -0500 [thread overview]
Message-ID: <20051104162529.GA24200@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <200511041408.29141.mblomenkamp@web.de>
On Fri, Nov 04, 2005 at 02:08:29PM +0100, Marcus Blomenkamp wrote:
> Hi all,
>
> i'm having serious problems getting my qemu instance running properly on linux
> framebuffer console. Somehow keystrokes are not delivered or translated
Yep. This is a known issue with the framebuffer. For some it seems to just work,
but for others the keys are not mapped correctly. My guess is that because qemu
uses the raw SDL scancode, its expected an X11 keycode but getting a framebuffer
keycode (or possibly the raw PC keyboard scancode). This probably wouldn't be
to hard for a person familiar with linux framebuffer programming to fix.
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
prev parent reply other threads:[~2005-11-04 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 13:08 [Qemu-devel] Keyboard/monitor problems when running not under X Marcus Blomenkamp
2005-11-04 16:25 ` Jim C. Brown [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=20051104162529.GA24200@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=mblomenkamp@web.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).