From: Rob Landley <rob@landley.net>
To: Olivier Danet <odanet@caramail.com>
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: Thu, 04 Jul 2013 07:18:11 -0500 [thread overview]
Message-ID: <1372940291.6645.0@driftwood> (raw)
In-Reply-To: <51CF4394.2030909@caramail.com> (from odanet@caramail.com on Sat Jun 29 15:29:08 2013)
On 06/29/2013 03:29:08 PM, Olivier Danet wrote:
> 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".
Yay! That fixes it. Thanks.
> - 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...
Or it could require a config tweak to the kernel, or some -mtune a
compile time. I'm happy enough with a different -cpu for sparc: I just
want to run the thing to natively compile software under emulation and
avoid more cross compiling.
Thanks,
Rob
next prev parent reply other threads:[~2013-07-07 18:26 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
2013-07-04 12:18 ` Rob Landley [this message]
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=1372940291.6645.0@driftwood \
--to=rob@landley.net \
--cc=blauwirbel@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=odanet@caramail.com \
--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.