All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marty E. Plummer" <hanetzer@startmail.com>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: Joel Stanley <joel@jms.id.au>,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: qemu/powernv: coreboot support?
Date: Sat, 19 Oct 2019 11:09:34 -0500	[thread overview]
Message-ID: <20191019160933.fizoc6tpu5jday4o@proprietary-killer> (raw)
In-Reply-To: <1cbd1882-15c8-5471-cd65-1c84c2920ba8@kaod.org>

[-- Attachment #1: Type: text/plain, Size: 2011 bytes --]

On Sat, Oct 19, 2019 at 05:53:12PM +0200, Cédric Le Goater wrote:
> On 19/10/2019 17:31, Marty E. Plummer wrote:
> > 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.
> >>
> >> However, you can bypass all this internal boot process by simply passing
> >> a -bios option and not passing a MTD device.
> >>
> > Doing so gives me the following error:
> > qemu-system-ppc64: Could not load OPAL firmware 'build/coreboot.rom'
> > (this is after I patched the 4mb size limit up)
> 
> Could you make that rom available ? 
> 
Sure, I think. Not sure about how sending files works in my current mail
client but will see. Its more or less a 'stock' (as stock as can be for
a new coreboot target) coreboot.rom file, but I've added some logic into
the build to fake a pnor ffs header at the end in order to trick hostboot
bootloader into loading it.
> Thanks,
> 
> C. 

[-- Attachment #2: coreboot.rom.gz --]
[-- Type: application/octet-stream, Size: 102985 bytes --]

  reply	other threads:[~2019-10-19 16:12 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 [this message]
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

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=20191019160933.fizoc6tpu5jday4o@proprietary-killer \
    --to=hanetzer@startmail.com \
    --cc=clg@kaod.org \
    --cc=david@gibson.dropbear.id.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.