From: Olivier Danet <odanet@caramail.com>
To: Rob Landley <rob@landley.net>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Openbios upgrade broke sparc32 linux.
Date: Sat, 29 Jun 2013 22:29:08 +0200 [thread overview]
Message-ID: <51CF4394.2030909@caramail.com> (raw)
In-Reply-To: <51CE03D4.1050505@ilande.co.uk>
On 28/06/2013 23:44, Mark Cave-Ayland wrote:
> On 28/06/13 03:08, Rob Landley wrote:
>
>> Commit 467b34689d27 upgraded the openbios image, and ever since my linux
>> system images hang about the time they try to initialize interrupts.
>>
>> http://landley.net/aboriginal/bin/system-image-sparc.tar.bz2
>>
>> Extract that and "./run-emulator.sh" in the tarball. Using qemu 1.2.0
>> for example works fine, you get a shell prompt. Using 1.5.0 hangs.
>>
>> Rob
>
> Hi Rob,
>
> Thanks for the bug report. I did a quick bisect on OpenBIOS and it
> points to the following commit:
>
> commit 167aafd70f64e74a77787ca5bf9f4dc750b27fc3
> Author: blueswirl <blueswirl@f158a5a8-5612-0410-a976-696ce0be7e32>
> Date: Sun Feb 3 16:50:11 2013 +0000
>
> SPARC32: microSPARC-II identification
>
> For the microSPARC-II = Fujitsu MB86904 = Sun STP1012PGA,
> PSR.IMPL=0 and PSR.VERS=4.
>
> This CPU model is used as default by QEMU when emulating
> a SparcStation-4 or SparcStation-5.
>
> Signed-off-by: Olivier DANET <odanet@caramail.com>
> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
>
>
> The commit itself is very simple and looks like this:
> http://git.qemu.org/?p=openbios.git;a=commitdiff;h=0fe772df8717ef75d91eae8ef221e9966ce2fd7f.
>
> My guess would be that Linux is trying to do some slightly different
> initialisation based upon identifying the CPU, but I'm not too
> familiar with the kernel code myself. Blue/Olivier - can either of you
> comment on this?
>
>
> ATB,
>
> Mark.
How embarrassing...
- QEMU 1.5.1 can boot Debian Etch (kernel 2.6.18), RedHat 4.2 (kernel
2.0.30), NetBSD 6.1 and OpenBSD 5.3.
- Your image (Linux 3.8) can be started with a TurboSparc CPU : qemu
-cpu "Fujitsu MB86907".
- My SparcStation-5 has a 110MHz MicroSPARC-II and the .attributes (aka
.properties) fields are identical
to OpenBIOS values, except for the mask_rev : I have 0x26, OpenBIOS sets
0x23
Before the patch, OpenBIOS had an incoherence between the PSR register
content and the BIOS defined values.
In Linux "arch/sparc/mm/srmmu.c:get_srmmu_type(void)", this correspond
to "a TurboSparc emulating Swift".
(Swift is the MS-2).
TurboSPARC could be the new QEMU default, but, ideally, the MS-II should
be preferred
as it is compatible with more OSes ( hoping to run NextStep in QEMU
one day ...).
Maybe recent Linux kernels are not compatible with the way QEMU emulates
the MS-II...
Regards
Olivier
[temlib.org]
next prev parent reply other threads:[~2013-06-29 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 2:08 [Qemu-devel] Openbios upgrade broke sparc32 linux Rob Landley
2013-06-28 21:44 ` Mark Cave-Ayland
2013-06-29 20:29 ` Olivier Danet [this message]
2013-07-04 12:18 ` Rob Landley
2013-07-04 21:52 ` Olivier Danet
2013-07-06 17:08 ` Rob Landley
2013-07-15 16:03 ` Mark Cave-Ayland
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=51CF4394.2030909@caramail.com \
--to=odanet@caramail.com \
--cc=blauwirbel@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
/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).