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>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] configs/qemu: Add a ppc64le-powernv8 configuration
Date: Tue, 11 Jan 2022 21:45:09 +0100 [thread overview]
Message-ID: <20220111214509.79c5c88e@windsurf> (raw)
In-Reply-To: <20220110210235.817082-1-clg@kaod.org>
Hello Cédric,
On Mon, 10 Jan 2022 22:02:33 +0100
Cédric Le Goater <clg@kaod.org> wrote:
> PowerNV is the platform using the OPAL [1] firmware on OpenPOWER
> systems. OPAL first loads a kernel and an initramfs image based on
> buildroot including a second boot loader petitboot [2]. The latter
> does device discovery and kexecs a new Linux image from disk or
> network.
>
> QEMU implements PowerNV machines [3] for the POWER8, POWER9 and
> Power10 processors which are used for dev and tests. POWER8 images
> being compatible with POWER9 and Power10, simply add a single
> qemu_ppc64le_powernv8 board for all.
>
> The QEMU script boots directly from a nvme disk because it is simple
> enough but a real system would boot from a ramfs first.
>
> [1] https://github.com/open-power/skiboot/blob/master/doc/overview.rst
> [2] https://github.com/open-power/petitboot/
> [3] https://qemu.readthedocs.io/en/latest/system/ppc/powernv.html
>
> Signed-off-by: Cédric Le Goater <clg@kaod.org>
> ---
> board/qemu/ppc64le-powernv8/readme.txt | 5 +++++
> configs/qemu_ppc64le_powernv8_defconfig | 29 +++++++++++++++++++++++++
> 2 files changed, 34 insertions(+)
> create mode 100644 board/qemu/ppc64le-powernv8/readme.txt
> create mode 100644 configs/qemu_ppc64le_powernv8_defconfig
Thanks, entire patch series applied. One small change was done: add
appropriate entries to the DEVELOPERS file, so that we know who to
contact for those defconfigs :-) Especially if our Gitlab CI
infrastructure detects build issues, you will be notified.
Since you are a PowerPC expert, I'd like to take this opportunity to
ask you about the toolchains we're providing at
https://toolchains.bootlin.com/. For the moment for PowerPC, we are
providing the following toolchains:
powerpc-440fp, not tested
powerpc64-e5500, tested with qemu_ppc64_e5500_defconfig
powerpc64-e6500, not tested
powerpc64le-power8, tested with qemu_ppc64le_pseries_defconfig
powerpc64-power8, tested with qemu_ppc64_pseries_defconfig
powerpc-e300c3, not tested
powerpc-e500mc, not tested
I suppose I could now test the powerpc-440fp toolchain with the
qemu_ppc_bamboo_defconfig you have added. Is that correct?
What about the other toolchain configurations? Is there some matching
Qemu emulation?
And generally speaking, does this selection of PowerPC architecture
variants make sense to offer pre-compiled toolchains? For quite a
while, we've had requests for other PowerPC variants:
https://github.com/bootlin/toolchains-builder/issues/2. Your input
would be very welcome :-)
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-11 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 21:02 [Buildroot] [PATCH 1/3] configs/qemu: Add a ppc64le-powernv8 configuration Cédric Le Goater
2022-01-10 21:02 ` [Buildroot] [PATCH 2/3] configs/qemu: Add a ppc-bamboo configuration Cédric Le Goater
2022-01-10 21:04 ` [Buildroot] [PATCH 1/3] configs/qemu: Add a ppc64le-powernv8 configuration Cédric Le Goater
2022-01-11 20:45 ` Thomas Petazzoni [this message]
2022-01-12 7:07 ` Cédric Le Goater
-- strict thread matches above, loose matches on Subject: below --
2022-01-10 20:58 Cédric Le Goater
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=20220111214509.79c5c88e@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=clg@kaod.org \
--cc=gerome.burlats@smile.fr \
--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