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: Tue, 28 Dec 2021 22:14:30 +0100	[thread overview]
Message-ID: <20211228221430.7e8cb844@windsurf> (raw)
In-Reply-To: <20211112160413.2736382-1-clg@kaod.org>

Hello Cédric,

On Fri, 12 Nov 2021 17:04:11 +0100
Cédric Le Goater <clg@kaod.org> wrote:

> PowerNV (as Non-Virtualized) is the "baremetal" platform using the
> OPAL [1] firmware. It runs Linux on IBM and OpenPOWER systems and can
> be used as an hypervisor OS, running KVM guests, or simply as a host
> OS. OPAL includes a Linux kernel and a buildroot rootfs which acts as
> a bootloader [2] for the various systems installed on disks.

For the person not familiar with all this OpenPOWER stuff, it's very
complex to understand all these firmware, virtualized stuff,
hypervisor, etc.

> diff --git a/board/qemu/ppc64le-powernv/readme.txt b/board/qemu/ppc64le-powernv/readme.txt
> new file mode 100644
> index 000000000000..ee102a3d6846
> --- /dev/null
> +++ b/board/qemu/ppc64le-powernv/readme.txt
> @@ -0,0 +1,5 @@
> +Run the emulation with:
> +
> +qemu-system-ppc64 -M powernv9 -kernel vmlinux -append "console=hvc0 rootwait root=/dev/nvme0n1" -device nvme,bus=pcie.3,addr=0x0,drive=drive0,serial=1234 -drive file=./rootfs.ext2,if=none,id=drive0,format=raw,cache=none -device e1000e,netdev=net0,mac=C0:FF:EE:00:01:03,bus=pcie.1,addr=0x0  -netdev user,id=net0 -serial mon:stdio -nographic # qemu_ppc64le_powernv_defconfig

You're emulating a powernv9, so we assume based on the Power9 processor.

> @@ -0,0 +1,29 @@
> +# Architecture
> +BR2_powerpc64le=y
> +BR2_powerpc_power8=y

But you're targeting Power8.

Could you clarify?

Thanks!

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

  parent reply	other threads:[~2021-12-28 21:14 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 ` Thomas Petazzoni [this message]
2021-12-28 22:50   ` [Buildroot] [PATCH 1/3] configs/qemu: Add a ppc64le-powernv configuration Cédric Le Goater
2021-12-29  8:50     ` Thomas Petazzoni
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=20211228221430.7e8cb844@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