From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Cédric Le Goater" <clg@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org,
"Peter Maydell" <peter.maydell@linaro.org>,
"Steven Lee" <steven_lee@aspeedtech.com>,
"Troy Lee" <leetroy@gmail.com>,
"Jamin Lin" <jamin_lin@aspeedtech.com>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Joel Stanley" <joel@jms.id.au>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Delevoryas" <peter@pjd.dev>
Subject: Re: [PATCH] aspeed: Deprecate the fby35 machine
Date: Fri, 05 Dec 2025 15:37:25 +0000 [thread overview]
Message-ID: <87ms3xq6ru.fsf@draig.linaro.org> (raw)
In-Reply-To: <20251126102424.927527-1-clg@redhat.com> ("Cédric Le Goater"'s message of "Wed, 26 Nov 2025 11:24:24 +0100")
Cédric Le Goater <clg@redhat.com> writes:
> There are no functional tests for the 'fby35' machine which makes
> harder to determine when something becomes deprecated or unused.
>
> The 'fby35' machine was originally added as an example of a multi-SoC
> system, with the expectation the models would evolve over time in an
> heterogeneous system. This hasn't happened and no public firmware is
> available to boot it. It can be replaced by the 'ast2700fc', another
> multi-SoC machine based on the newer AST2700 SoCs which are excepted
> to receive better support in the future.
Queued to pr/051225-10.2-final-fixes-1, thanks.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2025-12-05 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 10:24 [PATCH] aspeed: Deprecate the fby35 machine Cédric Le Goater
2025-12-03 7:42 ` Cédric Le Goater
2025-12-04 19:45 ` Peter Delevoryas
2025-12-05 8:43 ` Cédric Le Goater
2025-12-06 0:40 ` Peter Delevoryas
2025-12-05 15:37 ` Alex Bennée [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=87ms3xq6ru.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=andrew@codeconstruct.com.au \
--cc=clg@redhat.com \
--cc=jamin_lin@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=leetroy@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=peter@pjd.dev \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=steven_lee@aspeedtech.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).