From: Patrick Williams <patrick@stwcx.xyz>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Andrew Jeffery <andrew@aj.id.au>,
Amithash Prasad <amithash@fb.com>,
"open list:All patches CC here" <qemu-devel@nongnu.org>,
"open list:ASPEED BMCs" <qemu-arm@nongnu.org>,
Vijay Khemka <vijaykhemka@fb.com>, Joel Stanley <joel@jms.id.au>,
Karthikeyan Pasupathi <pkarthikeyan1509@gmail.com>,
Peter Delevoryas <pdel@fb.com>
Subject: Re: [PATCH v3] aspeed: Add support for the sonorapass-bmc board
Date: Wed, 1 Oct 2025 22:21:43 -0400 [thread overview]
Message-ID: <aN3ht1MdFppiDcPz@heinlein> (raw)
In-Reply-To: <0165086d-3ab4-4986-84ff-452984d16153@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
On Tue, Sep 30, 2025 at 07:51:15AM +0200, Cédric Le Goater wrote:
> Hello Patrick
>
> Would it be possible to contribute a functional test for this
> machine ?
>
> The request applies to these Facebook machines :
>
> sonorapass-bmc
This machine type is deprecated and never went to production.
> yosemitev2-bmc
> tiogapass-bmc
> fuji-bmc
> fby35-bmc
All of these are used by OpenBMC and/or Meta for QEMU validation of
new BMC images. I can get you an image for these if necessary.
>
> Since these machines contribute little to the Aspeed models,
> their value lies in the firmware they can run to exercise the
> models. Without functional tests, I plan to schedule their
> removal in the QEMU 10.2 cycle.
I don't understand this statement. What does "little value to the
Aspeed models" have to do with keeping machines in place. If we are
only going to have support for machines that you deem as "valuable" why
would anyone contribute a new machine? Is this a new policy that QEMU
only wants specific machine models for any particular SOC?
> The fby35-bmc value is in its multisoc nature. We now have the
> ast2700fc available as its replacement
We actually don't use the multisoc aspect of this machine. I'd be fine
if we drop those pieces specifically but the general "can the BMC image
boot" is regularly used.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-10-02 2:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 11:37 [PATCH] aspeed: Add support for the sonorapass-bmc board Patrick Williams
2020-05-01 15:26 ` no-reply
2020-05-04 6:43 ` Cédric Le Goater
2020-05-06 17:30 ` [PATCH v2] " Patrick Williams
2020-05-06 18:06 ` Amithash Prasad via
2020-05-06 18:28 ` Patrick Williams
2020-05-06 18:32 ` [PATCH v3] " Patrick Williams
2020-05-11 10:54 ` Peter Maydell
2020-05-11 13:13 ` Patrick Williams
2020-05-11 15:07 ` Peter Maydell
2020-05-14 11:05 ` Peter Maydell
2025-09-30 5:51 ` Cédric Le Goater
2025-10-02 2:21 ` Patrick Williams [this message]
2025-10-02 6:32 ` 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=aN3ht1MdFppiDcPz@heinlein \
--to=patrick@stwcx.xyz \
--cc=amithash@fb.com \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=pdel@fb.com \
--cc=peter.maydell@linaro.org \
--cc=pkarthikeyan1509@gmail.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vijaykhemka@fb.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;
as well as URLs for NNTP newsgroup(s).