From: Martin Bochnig <mb1x@gmx.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Q: SPARC Solaris as guest operating system with qemu?
Date: Thu, 01 Sep 2005 18:13:26 +0200 [thread overview]
Message-ID: <431728A6.5090404@gmx.com> (raw)
In-Reply-To: <200509011414.30524.heiko.nardmann@secunet.com>
Nardmann, Heiko wrote:
>how far is support for SPARC Solaris as a guest operating system inside qemu?
>
>
Latest public PROLL stuff has still the following problems:
>>From: "Blue Swirl" <blueswir1@hotmail.com>
>>To: renau@soe.ucsc.edu
>>Bcc:
>>Date: Mon, 15 Aug 2005 17:42:56 +0200
>>
>>
>>Here's a translation: Boot sector "bootblk" gets loaded. It reads 8k from
>>disk sd(0,2,0) (without partition code, mmh) at offset 8k. The contents is
>>not what is expected, so it prints "bootblk: not a UFS file system.". After
>>a couple of tries it gives up, prints "bootblk: can't find the boot
>>program." and halts.
>>
>>Looks like a problem with obp_devopen. I'll make a new Proll image soon.
>>
>I have read something about PROLL but did not understand what it is for or or
>how to use it. Can anyone shed some light onto it?
>
>
It is the emulated system's main firmware.
x86 target for example uses a "BIOS".
The SPARC target needs "PROLL". Physical SPARC's use OpenBootProm.
The PPC target needs "Open Hack'Ware". Physical PPC's use either
conventional "PREP" firmware, "OpenFirmware" CHRP or even
"VirtualOpenFirmware" loaded through floppy.
Some time ago you mentioned that you are actually using real SPARC machines.
Shouldn't you be well aware of, what OBP is?
See http://people.redhat.com/zaitcev/linux/ :
JavaStation and PROLL
My Krups
JavaStations come with two versions of PROM, 2.30 and 3.11. Linux works
with 2.30 out of the box. In 3.11 Sun changed virtual memory layout and
discarded an improtant interface (romvec). Thus 3.11 is not compatible
with Linux.
My solution for the PROM 3.11 problem is *Proll*. Proll is a PROM
replacement which takes over the machine instead of original PROM and
presents a 2.x interface to Linux kernel. Documentation is not available
yet but the code is easy to read as I hope. Current of Proll is *ID18*,
which supports all SPARC based JavaStations. Download it from the
following list.
* proll_18.tar.gz
<http://people.redhat.com/zaitcev/linux/proll_18.tar.gz>: Latest
source code.
* proll.version.h
<http://people.redhat.com/zaitcev/linux/proll.version.h>: Change log.
* proll.mrcoffee.ID18
<http://people.redhat.com/zaitcev/linux/proll.mrcoffee.ID18>:
Binary for JavaStation-1.
* proll.krups.ID18
<http://people.redhat.com/zaitcev/linux/proll.krups.ID18>: Binary
for JavaStation-NC, good for network bootstrapping and for flash.
* proll.krups-ser.ID18
<http://people.redhat.com/zaitcev/linux/proll.krups-ser.ID18>:
Binary for JavaStation-NC, same as above but with serial console.
* proll.espresso.ID18
<http://people.redhat.com/zaitcev/linux/proll.espresso.ID18>:
Binary for JavaStation-E, now the same joint codebase as Krups.
* proll.espresso-ser.ID18
<http://people.redhat.com/zaitcev/linux/proll.espresso-ser.ID18>:
Binary for JavaStation-E, same as above but with serial console.
I am not good at documenting stuff, but Robb Dubinski wrote a nice
HOWTO, located at http://www.tldp.org/HOWTO/JavaStation-HOWTO/index.html.
Jim Mintha has filesystem images at http://www.ultralinux.org/js. Those
are snapshots of a live system originally based on Red Hat 5.2.
On JavaStation-E a hardware fix
<http://people.redhat.com/zaitcev/notes/espresso_ide.txt> is needed to
get IDE interrupts.
next prev parent reply other threads:[~2005-09-01 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 12:14 [Qemu-devel] Q: SPARC Solaris as guest operating system with qemu? Nardmann, Heiko
2005-09-01 13:45 ` Martin Bochnig
2005-09-01 16:13 ` Martin Bochnig [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-01 15:41 Blue Swirl
2005-09-01 16:21 ` Martin Bochnig
2005-09-01 19:11 ` Blue Swirl
2005-09-02 9:02 ` Martin Bochnig
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=431728A6.5090404@gmx.com \
--to=mb1x@gmx.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.