qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "François Revol" <revol@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] atapi on ppc issue (was Re: qemu-system-ppc broken ?)
Date: Mon, 10 Nov 2008 21:27:32 +0100 CET	[thread overview]
Message-ID: <2564953043-BeMail@laptop> (raw)
In-Reply-To: <15BEECE3-2086-4EF9-9C89-3D458CB4AEC3@web.de>

> > The attached patch makes OpenHackware happy again.
> > At least qemu-system-ppc can now start debian iso, and mine as well
> [...]
> > OpenHackware should be fixed instead, but it seems the binary in
> > svn
> > has been updated after the last sources I found
> [...]
> > Seems the last update was already about ATAPI...
> > Anyone has the latest source used ?
> > I could at least fix it to check for bits on errors...
>
> Rene Rebe recently posted some diff against qemu's OHW diff, but it
> appeared to be whitespace-damaged.

Ohhh, I didn't even notice ohw.diff in pc-bios/ despite looking for
one!
I'll try to dig that one on gmane.org.

I just hope it's easier to build than OpenBIOS...

> > Of course it'd be much better to switch to a real OF instead...
> > but I don't have the time for that, couldn't find usable OpenBIOS
> > images,
>
> I once tried to get OpenBIOS working but failed, Laurent appeared to
> get some further - any update on that?

I tried building it for PPC yesterday, but I only had an powerpc-apple-
haiku- gcc around, and it didn't like it... Even after pointing it to
find our stdint.h and endian.h (WTF does it need OS headers to build a
BIOS ???).
It seems to be doing nasty things with m4 macros on C headers, really
ugly.

> > and it see[m]s CoreBoot v2 and v3 don't support ppc yet.
>
> I believe CoreBoot is unrelated to ppc, it replaces the x86 BIOS. It
> does allow to use OpenBIOS (Open Firmware) as payload but not the
> other direction - Blue Swirl used some assembler wizardry to
> bootstrap
> the sparc OpenBIOS.

CoreBoot actually supports more arch than just x86:
http://www.coreboot.org/Supported_Chipsets_and_Devices

But only v1 seemed to have ppc support.

François.

  reply	other threads:[~2008-11-10 20:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07  3:16 [Qemu-devel] qemu-system-ppc broken ? François Revol
2008-11-07  7:08 ` Aurelien Jarno
2008-11-07  7:53   ` François Revol
2008-11-07  8:19     ` [Qemu-devel] atapi on ppc issue (was Re: qemu-system-ppc broken ?) François Revol
2008-11-07  8:28       ` François Revol
2008-11-09 22:07         ` François Revol
2008-11-09 22:11           ` François Revol
2008-11-10 20:01           ` Andreas Färber
2008-11-10 20:27             ` François Revol [this message]
2008-11-10 20:56               ` Andreas Färber
2008-11-10 21:16                 ` François Revol
2008-11-11 17:31                   ` Blue Swirl
2008-11-11 17:58                     ` Andreas Färber
2008-11-11 17:28               ` Blue Swirl
2008-11-11 19:54             ` Laurent Vivier
2008-11-16 19:32               ` Blue Swirl
2008-11-16 19:40                 ` Laurent Vivier
2008-11-23 18:55                   ` Blue Swirl
2008-11-24  8:34                     ` René Rebe
2008-11-24 16:32                       ` Andreas Färber
2008-11-27 15:13                     ` Shin-ichiro KAWASAKI
2008-11-07 16:38   ` [Qemu-devel] qemu-system-ppc broken ? Laurent Desnogues
2008-11-08  8:57     ` Aurelien Jarno

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=2564953043-BeMail@laptop \
    --to=revol@free.fr \
    --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).