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 15:19:08 +0100 [thread overview]
Message-ID: <20211229151908.48d7d04e@windsurf> (raw)
In-Reply-To: <ac4e193e-3fcb-80df-a433-70664e5fb850@kaod.org>
Hello Cédric,
On Wed, 29 Dec 2021 15:01:30 +0100
Cédric Le Goater <clg@kaod.org> wrote:
> >> 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 ?
>
> Sure. Would you rather have a ppc64le-powernv8 and a ppc64le-powernv9
> config instead ?
In the interest of not growing too much the number of defconfigs, I
would perhaps suggest to have just a powernv8 configuration, and in its
readme.txt file, indicate that it can be similarly used on powerpcnv9.
> I have a few other patches adding similar boards for 44x CPUs. I can
> resend a v2 for the whole.
Sounds useful.
> What's the process to bump the QEMU version ?
Send a patch against the package/qemu/ package, it's as simple as that.
Ideally, when you do that, make sure to retest all the Qemu defconfigs,
to ensure they continue to boot well under the new Qemu version. You
can use Gitlab CI to automate this testing.
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
prev parent reply other threads:[~2021-12-29 14:19 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
2021-12-29 14:01 ` Cédric Le Goater
2021-12-29 14:19 ` Thomas Petazzoni [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=20211229151908.48d7d04e@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