qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org,
	The OpenBIOS Mailinglist <openbios@openbios.org>,
	coreboot@coreboot.org
Subject: Re: [Qemu-devel] atapi on ppc issue (was Re: qemu-system-ppc broken ?)
Date: Tue, 11 Nov 2008 19:28:18 +0200	[thread overview]
Message-ID: <f43fc5580811110928y3b85ab75yd6feae59e334361c@mail.gmail.com> (raw)
In-Reply-To: <2564953043-BeMail@laptop>

Crossposted to OpenBIOS and Coreboot lists.


On 11/10/08, François Revol <revol@free.fr> wrote:
> > > 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.

The M4 macro nastiness seems to be limited to the asm files only and
even then the macros  are not used. It should be possible to remove
the macros with little effort.

Maybe they are a leftover from something earlier?

>  > > 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.

Perhaps PPC support can be revived?

  parent reply	other threads:[~2008-11-11 17:28 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
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 [this message]
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=f43fc5580811110928y3b85ab75yd6feae59e334361c@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=coreboot@coreboot.org \
    --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).