From: "Andreas Färber" <afaerber@suse.de>
To: Bug 1004050 <1004050@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org, "Richard W.M. Jones" <rich@annexia.org>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [Bug 1004050] [NEW] qemu-system-ppc64 by default has non-working keyboard
Date: Fri, 25 May 2012 13:37:09 +0200 [thread overview]
Message-ID: <4FBF6EE5.6040007@suse.de> (raw)
In-Reply-To: <20120524165154.10792.50215.malonedeb@chaenomeles.canonical.com>
Am 24.05.2012 18:51, schrieb Richard W.M. Jones:
> Compile qemu from git and do:
>
> ./ppc64-softmmu/qemu-system-ppc64
>
> (ie. no parameters). It boots to an OpenBIOS prompt. However the
> keyboard doesn't work. After ~10 keypresses, qemu just says:
>
> usb-kbd: warning: key event queue full
> usb-kbd: warning: key event queue full
> usb-kbd: warning: key event queue full
> usb-kbd: warning: key event queue full
>
> There is no indication inside the guest that OpenBIOS is seeing keyboard
> events.
>
> Also there's no indication of what type of keyboard devices are
> available, nor what we should use.
OpenBIOS/ppc only supports ADB keyboards at this time. ppc64 kernels
don't support ADB though, so -M mac99 has a USB keyboard. -nographic
should work, and so does -M pseries (using SLOF).
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-05-25 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 16:51 [Qemu-devel] [Bug 1004050] [NEW] qemu-system-ppc64 by default has non-working keyboard Richard W.M. Jones
2012-05-25 11:37 ` Andreas Färber [this message]
2012-07-18 19:27 ` [Qemu-devel] [Bug 1004050] " Truman Boyes
2017-02-13 20:14 ` Thomas Huth
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=4FBF6EE5.6040007@suse.de \
--to=afaerber@suse.de \
--cc=1004050@bugs.launchpad.net \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=rich@annexia.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).