From: Aurelien Jarno <aurel32@debian.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1110531] Re: regression booting pxa kernels
Date: Mon, 20 May 2013 17:32:44 -0000 [thread overview]
Message-ID: <20130520173246.1020.83023.launchpad@soybean.canonical.com> (raw)
In-Reply-To: 20130130160710.1785.43097.malonedeb@soybean.canonical.com
** Changed in: qemu
Status: Fix Committed => 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/1110531
Title:
regression booting pxa kernels
Status in QEMU:
Fix Released
Bug description:
Somewhere between qemu 1.1.2 and 1.2.0 OpenBSD zaurus kernels and
ramdisk images stopped booting properly and instead end up in the
kernel debugger. This behaviour is still present in the latest git
and appears to have been introduced in:
commit e2f8a44d0d425a22cca5855702f534536f5e8c90
Author: Peter Maydell <peter.maydell@linaro.org>
Date: Wed Jun 20 11:57:07 2012 +0000
hw/pxa2xx.c: Convert CLKCFG and PWRMODE cp14 regs
Convert the PXA2xx CLKCFG and PWRMODE cp14 registers to the
new arm_cp_reginfo scheme.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
To duplicate this behaviour:
http://ftp.openbsd.org/pub/OpenBSD/5.2/zaurus/bsd.rd
$ qemu-system-arm -M spitz -serial stdio -kernel bsd.rd -portrait
should boot to an install prompt.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1110531/+subscriptions
prev parent reply other threads:[~2013-05-20 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130130160710.1785.43097.malonedeb@soybean.canonical.com>
2013-02-02 13:57 ` [Qemu-devel] [Bug 1110531] Re: regression booting pxa kernels Peter Maydell
2013-02-02 15:02 ` Peter Maydell
2013-02-02 15:28 ` Peter Maydell
2013-02-02 15:46 ` Brad Smith
2013-05-20 17:32 ` Aurelien Jarno [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=20130520173246.1020.83023.launchpad@soybean.canonical.com \
--to=aurel32@debian.org \
--cc=1110531@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 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).