From: Blue Swirl <blauwirbel@gmail.com>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: The OpenBIOS Mailinglist <openbios@openbios.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>
Subject: [Qemu-devel] Re: [RFT] ppc64 OpenBIOS
Date: Sat, 18 Dec 2010 16:33:03 +0000 [thread overview]
Message-ID: <AANLkTi=gSFVM_oF==deZzHgm+twLYZkcTr4+rCr7G3Ju@mail.gmail.com> (raw)
In-Reply-To: <AC118BB3-87F6-44A0-9299-7D259AA2CF0F@web.de>
On Sat, Dec 18, 2010 at 2:30 AM, Andreas Färber <andreas.faerber@web.de> wrote:
> Hello,
>
> Except for some fs/iso9660/ issues, ppc64 guests are booting for me with the
> last five OpenBIOS patches posted.
What are the issues?
>
> You can find them together with the config change to use fs/grubfs/ here:
>
> git://repo.or.cz/openbios/afaerber.git ppc64-boot
>
> Please test your favorite ppc64 kernels and images with
> obj-ppc64/openbios-qemu.elf!
Passes my simple tests. The only problem is that building forthstrap
on a 64 bit host fails.
> If I don't hear of regressions, I'll commit those patches. Once that is done
> and the iso9660 issues hopefully fixed, I would ask for Blue to commit
> openbios-ppc and openbios-ppc64 blobs to QEMU. I'll then prepare a QEMU
> patch to switch the default qemu-system-ppc64 ppc_newworld.c BIOS from
> openbios-ppc to openbios-ppc64.
I think openbios-ppc should be renamed to openbios-ppc32 for
consistency with Sparc naming.
next prev parent reply other threads:[~2010-12-18 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-18 2:30 [Qemu-devel] [RFT] ppc64 OpenBIOS Andreas Färber
2010-12-18 16:33 ` Blue Swirl [this message]
2010-12-18 16:54 ` [Qemu-devel] Re: [OpenBIOS] " Andreas Färber
2010-12-18 18:55 ` 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='AANLkTi=gSFVM_oF==deZzHgm+twLYZkcTr4+rCr7G3Ju@mail.gmail.com' \
--to=blauwirbel@gmail.com \
--cc=agraf@suse.de \
--cc=andreas.faerber@web.de \
--cc=openbios@openbios.org \
--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).