Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: Gerome Burlats <gerome.burlats@smile.fr>,
	Romain Naour <romain.naour@gmail.com>,
	Matt Weber <matthew.weber@collins.com>,
	Joel Stanley <joel@jms.id.au>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] configs/qemu: Add a ppc64le-powernv configuration
Date: Wed, 29 Dec 2021 09:50:40 +0100	[thread overview]
Message-ID: <20211229095040.43a2bb32@windsurf> (raw)
In-Reply-To: <f7dc4424-a38a-c448-4436-f1e06b86ffb9@kaod.org>

Hello Cédric,

On Tue, 28 Dec 2021 23:50:29 +0100
Cédric Le Goater <clg@kaod.org> wrote:

> Let's try differently,
> 
> On these systems, the FW is comparable to U-Boot as it loads kernel and
> initramfs images from flash. The initramfs is a buildroot environment
> which includes the petitboot [*] boot loader. This second boot loader
> does the device discovery and kexecs a new Linux image from disk or
> network.
> 
> What we care about here is only the first level which uses the buildroot
> image. petitboot is another topic.
> 
> As for QEMU, it implements 3 machines POWER8, POWER9 and Power10
> processors that we use for dev and tests. I have chosen in the QEMU
> script to boot directly from a nvme disk because it is simple enough
> but using a ramfs would be closer to reality.
> 
> The hypervisor part is simply a feature of this Linux PPC platform,
> that is called PowerNV.
> 
> [*] https://github.com/open-power/petitboot/

Thanks for the additional explanations!

> > Could you clarify?  
> 
> because the same image can be used for the QEMU machine implementing
> the POWER8 processor, which also works for POWER9 and Power10.

So why don't we test it with -M powernv8 ?

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-12-29  8:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 16:04 [Buildroot] [PATCH 1/3] configs/qemu: Add a ppc64le-powernv configuration Cédric Le Goater
2021-11-12 16:04 ` [Buildroot] [PATCH 2/3] configs/qemu_ppc64_e5500: Enable dhcp on network interface Cédric Le Goater
2021-12-28 21:15   ` Thomas Petazzoni
2021-11-12 16:04 ` [Buildroot] [PATCH 3/3] configs/qemu_ppc_e500mc: " Cédric Le Goater
2021-12-28 21:15   ` Thomas Petazzoni
2021-12-28 21:14 ` [Buildroot] [PATCH 1/3] configs/qemu: Add a ppc64le-powernv configuration Thomas Petazzoni
2021-12-28 22:50   ` Cédric Le Goater
2021-12-29  8:50     ` Thomas Petazzoni [this message]
2021-12-29 14:01       ` Cédric Le Goater
2021-12-29 14:19         ` Thomas Petazzoni

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=20211229095040.43a2bb32@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=clg@kaod.org \
    --cc=gerome.burlats@smile.fr \
    --cc=joel@jms.id.au \
    --cc=matthew.weber@collins.com \
    --cc=romain.naour@gmail.com \
    /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