qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: Peter Delevoryas <peter@pjd.dev>
Cc: "Cédric Le Goater" <clg@redhat.com>,
	qemu-devel@nongnu.org, qemu-arm@nongnu.org,
	"Maydell Peter" <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>
Subject: Re: [PATCH] aspeed: Deprecate the fby35 machine
Date: Fri, 5 Dec 2025 09:43:15 +0100	[thread overview]
Message-ID: <f0cb1f8e-bccd-4360-911a-f74560a350a8@kaod.org> (raw)
In-Reply-To: <2B4B594F-DFB1-4BD1-8FF3-8F74EB2EC52A@pjd.dev>

On 12/4/25 20:45, Peter Delevoryas wrote:
> 
> 
>> On Dec 2, 2025, at 11:42 PM, Cédric Le Goater <clg@kaod.org> wrote:
>>
>> Hello,
>>
>>> On 11/26/25 11:24, Cédric Le Goater wrote:
>>> 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.
>>> Cc: Peter Delevoryas <peter@pjd.dev>
>>> Signed-off-by: Cédric Le Goater <clg@redhat.com>
>>
>>
>> No objections ? If not, I will queue the deprecation for QEMU 10.2.
>> Since deprecation is tolerated in the -rc phase.
> 
> Oh hey, sorry I missed the original email, yeah no objections! Totally fair. :) We’re not using this internally either, we’ve mostly ended up pursuing multi-process solutions. 

Could we have your Acked-by then ?

> Even though I think single-process stuff is interesting, getting multi master i2c to work between socs in the same process can be tricky.

Yeah. This is still WIP. Making good progres though.

Thanks,

C.




  reply	other threads:[~2025-12-05  8:44 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 [this message]
2025-12-06  0:40       ` Peter Delevoryas
2025-12-05 15:37 ` Alex Bennée

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=f0cb1f8e-bccd-4360-911a-f74560a350a8@kaod.org \
    --to=clg@kaod.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).