From: Paul Brook <paul@codesourcery.com>
To: Blue Swirl <blueswir1@hotmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Switch to OpenBIOS for Sparc32/64?
Date: Wed, 7 Jun 2006 20:48:42 +0100 [thread overview]
Message-ID: <200606072048.43573.paul@codesourcery.com> (raw)
In-Reply-To: <BAY104-F348F415D172C2E716DE99FFF8A0@phx.gbl>
On Wednesday 07 June 2006 20:24, Blue Swirl wrote:
> >Sounds like a good idea to me, and the sooner the better.
> >Even if we find some things that work with proll but not openbios I guess
> >there's a good chance of getting openbios fixed.
>
> So I'll send you a patch that changes the name 'proll.elf' to
> 'openbios-builtin.elf' (or maybe it's better to use something like
> 'openbios-sparc32', simplifies the code) and a sample OpenBIOS file and
> that's it?
Yes. Plus documentation bits.
Bonus points if you include a README describing where the bios comes from and
basic description of how to reproduce it, even if this is just "download the
openbios sources and they should just work".
Paul
next prev parent reply other threads:[~2006-06-07 19:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 15:56 [Qemu-devel] Switch to OpenBIOS for Sparc32/64? Blue Swirl
2006-06-07 16:17 ` Paul Brook
2006-06-07 16:38 ` Natalia Portillo
2006-06-07 16:54 ` Joshua Root
2006-06-07 17:01 ` Natalia Portillo
2006-06-07 17:39 ` [Qemu-devel] Switch to OpenBIOS for PowerPC? (was: Switch to OpenBIOS for Sparc32/64?) Joshua Root
2006-06-07 18:27 ` Natalia Portillo
2006-06-07 19:24 ` [Qemu-devel] Switch to OpenBIOS for Sparc32/64? Blue Swirl
2006-06-07 19:48 ` Paul Brook [this message]
2006-06-07 21:03 ` [Qemu-devel] Good news for Gentoo Linux users Natalia Portillo
2006-06-08 9:03 ` Jan Marten Simons
2006-06-08 12:32 ` Natalia Portillo
-- strict thread matches above, loose matches on Subject: below --
2006-06-08 15:40 [Qemu-devel] Switch to OpenBIOS for Sparc32/64? Blue Swirl
2006-06-08 21:45 ` Fabrice Bellard
2006-06-14 12:22 ` Fabrice Bellard
2006-06-09 2:09 Armistead, Jason
2006-06-18 9:29 Blue Swirl
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=200606072048.43573.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=blueswir1@hotmail.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).