** 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 des
** Changed in: qemu
Status: New => Fix Committed
--
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 Committed
Bug description
Thank you Peter for the quick response to this bug report.
--
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:
New
Bug description:
Som
Fixed by this patch http://patchwork.ozlabs.org/patch/217673/ which
hopefully will make it into 1.4.
--
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
Sta
Ah, found the problem -- it looks like I accidentally transposed the
crm/crn values for all the perf registers in commit dc2a9045c, in the
process of converting from switch statements to the table
representation, and my test Linux image obviously doesn't prod these
registers. I'll send out a patch.
OpenBSD appears to be trying to access cp14 crn=0 crm=1 opc1=0 opc2=0.
Implementing this as a no-op allows the image to boot.
I'm trying to track down what this is supposed to be -- it doesn't seem to be
listed in the PXA27x docs.
(Previously we were lax about decoding and tended to print warnin
