From: Thomas Huth <1004050@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1004050] Re: qemu-system-ppc64 by default has non-working keyboard
Date: Mon, 13 Feb 2017 20:14:51 -0000 [thread overview]
Message-ID: <20170213201451.29932.27099.malone@gac.canonical.com> (raw)
In-Reply-To: 20120524165154.10792.50215.malonedeb@chaenomeles.canonical.com
AFAIK an OHCI driver has been added to OpenBIOS in 2014, so marking this
bug as fixed now. If you still have issues with OpenBIOS, please report
them to the OpenBIOS project instead of the QEMU bug tracker, thanks!
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1004050
Title:
qemu-system-ppc64 by default has non-working keyboard
Status in QEMU:
Fix Released
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1004050/+subscriptions
prev parent reply other threads:[~2017-02-13 20:24 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
2012-07-18 19:27 ` [Qemu-devel] [Bug 1004050] " Truman Boyes
2017-02-13 20:14 ` Thomas Huth [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=20170213201451.29932.27099.malone@gac.canonical.com \
--to=1004050@bugs.launchpad.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.