From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] sparc32 fix carry flag handling (Solaris bootblk fix)
Date: Fri, 13 Nov 2009 15:28:38 +0100 [thread overview]
Message-ID: <fb8d4f70911130628m284facedn80e9fb3e4f62e16e@mail.gmail.com> (raw)
In-Reply-To: <fb8d4f70911051248l56e01d13le023d7140e75f52e@mail.gmail.com>
>> Could you describe the steps how to boot Solaris with OBP? I'm sure
>> there are a lot of people who'd like to test if their favorite Sparc
>> Solaris programs work on QEMU.
Gathered things for which I currently have hacks here:
http://tyom.blogspot.com/2009/11/things-missing-in-vanilla-qemu.html
Actually for OBP itself it's just two (SS-5) or three (SS-20) things:
- Floppy. Instead of fixing it, I broke it completely, so OBP doesn't
try to initialize it and hang. Actually it maybe not the fdc itself,
but the irq handling. There are OBP tests which may help to understand
what is currently going wrong. I didn't need it, does the fdc actually
work under linux/netbsd/OpenBIOS?
- [SparcStation-5] 0x6e000000 AFX. OBP tries to access it and fails
with "unassigned address exception". Is only present in the SS-5's
TCX. The required address space is just one byte long. IMHO makes no
sense to create a special stub device for it. Can we push it into the
TCX?
- [SparcStation-20] 0xef8010000 DBRI, 0x9000X00X FCode SIMMs.
"unassigned address exception".
AFX, DBRI and FCode SIMMs can be implemented as stubs. Yet better
would be if SBUS probing would do a proper fault. This devices seem to
be optional.
next prev parent reply other threads:[~2009-11-13 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 23:58 [Qemu-devel] [PATCH] sparc32 fix carry flag handling (Solaris bootblk fix) Artyom Tarasenko
2009-11-04 19:44 ` [Qemu-devel] " Blue Swirl
2009-11-05 20:48 ` Artyom Tarasenko
2009-11-13 14:28 ` Artyom Tarasenko [this message]
2009-11-13 21:01 ` Blue Swirl
2009-12-10 18:27 ` Artyom Tarasenko
2009-12-12 9:07 ` Blue Swirl
2009-12-16 16:41 ` Artyom Tarasenko
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=fb8d4f70911130628m284facedn80e9fb3e4f62e16e@mail.gmail.com \
--to=atar4qemu@googlemail.com \
--cc=blauwirbel@gmail.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 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).