From: Michael Ellerman <michael@ellerman.id.au>
To: David Gibson <dwg@au1.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 2/2] powerpc: Add an ePAPR compliant boot wrapper
Date: Thu, 14 Apr 2011 14:25:32 +1000 [thread overview]
Message-ID: <1302755132.12513.92.camel@concordia> (raw)
In-Reply-To: <20110414004303.GZ3151@yookeroo>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On Thu, 2011-04-14 at 10:43 +1000, David Gibson wrote:
> On Wed, Apr 13, 2011 at 09:05:12AM -0400, Josh Boyer wrote:
> > On Wed, Apr 13, 2011 at 04:38:56PM +1000, Michael Ellerman wrote:
> > >+++ b/arch/powerpc/boot/epapr.c
> > >@@ -0,0 +1,69 @@
> > >+/*
> > >+ * Bootwrapper for ePAPR compliant firmwares
> >
> > Out of curiosity, do we have a list of the ePAPR compliant firmwares (if
> > any)?
>
> The one this has been tested with is a revised (internal, so far)
> version of SLOF. For the platform that I believe Michael is in the
> middle of upstreaming support for.
Yep.
> > >+#include "ops.h"
> > >+#include "stdio.h"
> > >+#include "planetcore.h"
> > >+#include "dcr.h"
> > >+#include "4xx.h"
> > >+#include "io.h"
> >
> > Do you need planetcore, dcr, and 4xx.h included here? I don't see
> > anything used that would require them.
>
> Ah, no. Leftovers from the files I based this on, I think.
I'll send a new version.
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-04-14 4:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 6:38 [PATCH 1/2] powerpc: Allow building the zImage wrapper as a relocatable ET_DYN Michael Ellerman
2011-04-13 6:38 ` [PATCH 2/2] powerpc: Add an ePAPR compliant boot wrapper Michael Ellerman
2011-04-13 13:05 ` Josh Boyer
2011-04-14 0:43 ` David Gibson
2011-04-14 4:25 ` Michael Ellerman [this message]
2011-04-15 4:29 ` Michael Ellerman
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=1302755132.12513.92.camel@concordia \
--to=michael@ellerman.id.au \
--cc=dwg@au1.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).