From: David Gibson <david@gibson.dropbear.id.au>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: "Marty E. Plummer" <hanetzer@startmail.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Joel Stanley <joel@jms.id.au>
Subject: Re: qemu/powernv: coreboot support?
Date: Sun, 20 Oct 2019 17:24:16 +1100 [thread overview]
Message-ID: <20191020062416.GG1960@umbus.fritz.box> (raw)
In-Reply-To: <21ba3404-dcd3-fe06-7725-d58e249f9fd2@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]
On Sat, Oct 19, 2019 at 03:46:59PM +0200, Cédric Le Goater wrote:
> On 18/10/2019 19:28, Marty E. Plummer wrote:
> > Hello,
> >
> > First off, thank you for the work you've done on the ppc64 support, it
> > has been very useful. I'm currently working on a coreboot port for the
> > talos ii line of systems (which means more ppc64 support, support
> > specifically for the power9 sforza chip, and specific mainboard support.
> > My plate is very full lol) and have been using qemu to debug the
> > bootblock.
> >
> > It has been very useful for that, but I'm now at the point where I need
> > to jump to romstage, and that's where it gets tricky. qemu parses the rom
> > image and looks for a ffs header, locates skiboot on it, and jumps straight
> > to that. Not exactly ideal for debugging something not produced from op-build.
>
> yes. I suppose you are using my branch powernv-4.2 which adds PNOR support
> and a way to boot directly from PNOR. In that case, QEMU parses the PNOR
> file to extract the PAYLOAD partition (skiboot). skiboot also detects the
> flash and extract the kernel and initramfs from the PNOR.
Ah! Now I understand. I hadn't looked at that branch, so I had no
idea what all this pnor stuff was about. In mainline we just load
skiboot as a normal firmware file and jump into it.
> However, you can bypass all this internal boot process by simply passing
> a -bios option and not passing a MTD device.
Right.
> I haven't published the PNOR support and the boot from PNOR yet. Lack
> of time and because sPAPR is the priority.
>
> > Do you think it would be within your wheelhouse to provide a generic, non-ffs
> > pnor interface for loading arbitary rom images?
>
> I should probably send the PNOR patchset now so that we can discuss on
> a better way to satisfy all needs.
>
> > It would be of great help if
> > you could. (This would still hopefully have the bmc support code as
> > well, as I'm still needing to support a system using one).
>
> We have support for Aspeed machines AST2400, AST2500 and AST2600. It
> is possible to interconnect them through the BT device. Or you can use
> the IPMI BT simulator of QEMU on the PowerNV machine
>
> Thanks,
>
> C.
>
--
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 --]
prev parent reply other threads:[~2019-10-20 6:36 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
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 [this message]
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=20191020062416.GG1960@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).