From: Mike Russo <greatquux@gmail.com>
To: jasper.lowell@bt.com
Cc: tony.nguyen@bt.com, mark.cave-ayland@ilande.co.uk,
dgilbert@redhat.com, qemu-devel@nongnu.org,
peter.tribble@gmail.com, atar4qemu@gmail.com
Subject: Re: Emulating Solaris 10 on SPARC64 sun4u
Date: Wed, 20 May 2020 13:44:33 -0400 [thread overview]
Message-ID: <b7b2d3921fa6d2274c63b8b58f655bf293139598.camel@gmail.com> (raw)
In-Reply-To: <be68b7ad559ec17c69439217c1378c23e30745c9.camel@bt.com>
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
> Using the proprietary firmware for this would be ideal. It would also
> provide reliable access to the kernel debugger which would be
> extremely
> helpful for diagnosing what's going wrong with the console. I'm not
> sure how I would go about making progress on this though. I know there
> are binaries of the BIOS for Sun4m machines floating around but I'm
> not
> aware of any for Sun4u machines.
>
I haven't been able to find any of this firmware either. Not sure if
this helps but someone says they've got the Ultra 1 firmware (along with
cgsix and cgthree) available here:
https://people.csail.mit.edu/fredette/tme/sun-u1-nbsd.html
[-- Attachment #2: Type: text/html, Size: 1007 bytes --]
next prev parent reply other threads:[~2020-05-20 21:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 6:31 Emulating Solaris 10 on SPARC64 sun4u jasper.lowell
2020-02-05 17:33 ` Dr. David Alan Gilbert
2020-02-07 5:43 ` jasper.lowell
2020-02-08 0:03 ` BALATON Zoltan
2020-02-10 15:38 ` BALATON Zoltan
2020-02-10 19:04 ` John Snow
2020-02-10 22:32 ` Missing IRQ with bmdma on ppc/mips/sparc? (was: Re: Emulating Solaris 10 on SPARC64 sun4u) BALATON Zoltan
2020-02-25 20:55 ` IDE IRQ problem after UDMA enabled " BALATON Zoltan
2020-02-25 22:00 ` BALATON Zoltan
2020-02-25 22:12 ` Emulating Solaris 10 on SPARC64 sun4u BALATON Zoltan
2020-02-09 11:26 ` Mark Cave-Ayland
2020-02-19 3:42 ` jasper.lowell
2020-02-19 18:54 ` BALATON Zoltan
2020-02-19 20:10 ` BALATON Zoltan
2020-02-21 19:53 ` Dr. David Alan Gilbert
2020-02-28 22:05 ` BALATON Zoltan
2020-03-01 0:15 ` BALATON Zoltan
2020-05-07 14:29 ` jasper.lowell
2020-05-07 15:02 ` Artyom Tarasenko
2020-05-08 2:33 ` jasper.lowell
2020-05-08 8:51 ` Peter Tribble
2020-05-08 13:45 ` Artyom Tarasenko
2020-05-10 2:46 ` jasper.lowell
2020-05-10 9:22 ` Mark Cave-Ayland
2020-05-17 7:57 ` jasper.lowell
2020-05-17 12:37 ` Artyom Tarasenko
2020-05-18 2:56 ` jasper.lowell
2020-05-20 17:44 ` Mike Russo [this message]
2020-05-07 18:54 ` BALATON Zoltan
2020-05-08 2:55 ` jasper.lowell
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=b7b2d3921fa6d2274c63b8b58f655bf293139598.camel@gmail.com \
--to=greatquux@gmail.com \
--cc=atar4qemu@gmail.com \
--cc=dgilbert@redhat.com \
--cc=jasper.lowell@bt.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=peter.tribble@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=tony.nguyen@bt.com \
/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).