From: David Gibson <david@gibson.dropbear.id.au>
To: "Marty E. Plummer" <hanetzer@startmail.com>
Cc: "Joel Stanley" <joel@jms.id.au>,
qemu-ppc@nongnu.org, "Cédric Le Goater" <clg@kaod.org>,
qemu-devel@nongnu.org
Subject: Re: qemu/powernv: coreboot support?
Date: Tue, 22 Oct 2019 18:55:23 +1100 [thread overview]
Message-ID: <20191022075523.GK6439@umbus.fritz.box> (raw)
In-Reply-To: <20191022021754.eliz2epsusf4qbdl@proprietary-killer>
[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]
On Mon, Oct 21, 2019 at 09:17:55PM -0500, Marty E. Plummer wrote:
> On Tue, Oct 22, 2019 at 12:40:32PM +1100, David Gibson wrote:
> > On Mon, Oct 21, 2019 at 07:32:09PM -0500, Marty E. Plummer wrote:
> > > On that note, is qemu-ppc64 currently capable of running LE
> > > firmware?
> >
> > Well.. "qemu-ppc64" as such isn't capable of running either LE or
> > firmware, since that's the Linux userspace emulator.
> > qemu-system-ppc64 *is* capable of running both LE and BE firmwares though.
> >
> Ah. yeah, that's what I meant. Good to know.
Paul Mackerras came up with some magic code that can get you from an
unknown endian state to a known state.
> > Your firmware will, however, need a tiny BE shim to switch the cpu
> > into LE mode.
> >
> Yeah, I figured as much, and was planning to have a shim available for
> 'real' hardware in the event a user wants to run coreboot in LE mode
> after both work properly (though somewhere in the OpenPOWER spec it is
> stated firmware must be BE).
TBH, it makes no sense to specify the endianness of the firmware -
it's an internal detail. The endianness of the firmware *interfaces*
needs to be fixed of course, but not the endianness of the
implementation.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-10-22 7:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 17:28 qemu/powernv: coreboot support? Marty E. Plummer
2019-10-19 11:15 ` David Gibson
2019-10-19 12:28 ` Marty E. Plummer
2019-10-19 13:46 ` Cédric Le Goater
2019-10-19 15:31 ` Marty E. Plummer
2019-10-19 15:53 ` Cédric Le Goater
2019-10-19 16:09 ` Marty E. Plummer
2019-10-20 6:28 ` David Gibson
2019-10-20 6:51 ` Cédric Le Goater
2019-10-20 16:32 ` Marty E. Plummer
2019-10-21 5:34 ` David Gibson
2019-10-21 12:46 ` Cédric Le Goater
2019-10-22 0:32 ` Marty E. Plummer
2019-10-22 1:40 ` David Gibson
2019-10-22 2:17 ` Marty E. Plummer
2019-10-22 7:55 ` David Gibson [this message]
2019-10-22 7:58 ` Cédric Le Goater
2019-10-23 21:41 ` Marty E. Plummer
2019-10-19 18:51 ` Marty E. Plummer
2019-10-19 19:23 ` Marty E. Plummer
2019-10-20 19:48 ` Peter Maydell
2019-10-21 9:51 ` Philippe Mathieu-Daudé
2019-10-20 6:26 ` David Gibson
2019-10-20 6:24 ` David Gibson
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=20191022075523.GK6439@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=clg@kaod.org \
--cc=hanetzer@startmail.com \
--cc=joel@jms.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).