qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: etanous via <qemu-devel@nongnu.org>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
	Steven Lee <steven_lee@aspeedtech.com>,
	Joel Stanley <joel@jms.id.au>, Troy Lee <leetroy@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Andrew Jeffery <andrew@codeconstruct.com.au>,
	Jamin Lin <jamin_lin@aspeedtech.com>,
	qemu-arm@nongnu.org
Subject: Re: [PATCH 0/4] Add support for gb200-bmc machine
Date: Wed, 2 Jul 2025 12:31:39 -0700	[thread overview]
Message-ID: <aGWJG1fO0vmL_RyU@edtanousvm.nvidia.com> (raw)
In-Reply-To: <b70dbdb3-0d1e-4976-b696-78065bd09640@kaod.org>

On Wed, Jul 02, 2025 at 09:00:53AM +0200, Cédric Le Goater wrote:
> External email: Use caution opening links or attachments
> 
> 
> On 7/1/25 22:33, Ed Tanous wrote:
> > This patch series adds support for gb200-bmc, a baseboard management controller
> > module based on an Aspeed 2600 SOC.
> > 
> > Ed Tanous (4):
> >    hw/arm: Add PCA9554 to ARM target
> >    hw/arm/aspeed: Add second SPI chip to Aspeed model
> >    docs: add support for gb200-bmc
> >    hw/arm/aspeed: Add GB200 BMC target
> > 
> >   docs/system/arm/aspeed.rst |  4 +-
> >   hw/arm/Kconfig             |  1 +
> >   hw/arm/aspeed.c            | 81 ++++++++++++++++++++++++++++++++++++++
> >   hw/arm/aspeed_eeprom.c     | 21 ++++++++++
> >   hw/arm/aspeed_eeprom.h     |  3 ++
> >   include/hw/arm/aspeed.h    |  2 +
> >   6 files changed, 110 insertions(+), 2 deletions(-)
> > 
> 
> Could you provide a functional test for the gb200nvl-bmc machine too ?
> See tests/functional/test_*aspeed* files.
> 

Can do.  It looks like images are pushed to
https://github.com/legoater/qemu-aspeed-boot and accepted via Github PR?
Will open PR shortly.

> Thanks,
> 
> C.
> 
> 


  reply	other threads:[~2025-07-02 19:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 20:33 [PATCH 0/4] Add support for gb200-bmc machine Ed Tanous
2025-07-01 20:33 ` [PATCH 1/4] hw/arm: Add PCA9554 to ARM target Ed Tanous
2025-07-02  6:47   ` Cédric Le Goater
2025-07-02  7:04     ` Philippe Mathieu-Daudé
2025-07-02 19:20       ` etanous via
2025-07-02 21:21         ` Cédric Le Goater
2025-07-02 19:18     ` etanous via
2025-07-01 20:33 ` [PATCH 2/4] hw/arm/aspeed: Add second SPI chip to Aspeed model Ed Tanous
2025-07-02  7:00   ` Cédric Le Goater
2025-07-02 19:27     ` etanous via
2025-07-02 21:23       ` Cédric Le Goater
2025-07-02 21:32   ` Cédric Le Goater
2025-07-01 20:33 ` [PATCH 3/4] docs: add support for gb200-bmc Ed Tanous
2025-07-02  6:49   ` Cédric Le Goater
2025-07-01 20:34 ` [PATCH 4/4] hw/arm/aspeed: Add GB200 BMC target Ed Tanous
2025-07-02 21:38   ` Cédric Le Goater
2025-07-02 22:04     ` Ed Tanous via
2025-07-02  7:00 ` [PATCH 0/4] Add support for gb200-bmc machine Cédric Le Goater
2025-07-02 19:31   ` etanous via [this message]
2025-07-02 21:25     ` 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=aGWJG1fO0vmL_RyU@edtanousvm.nvidia.com \
    --to=qemu-devel@nongnu.org \
    --cc=andrew@codeconstruct.com.au \
    --cc=clg@kaod.org \
    --cc=etanous@nvidia.com \
    --cc=jamin_lin@aspeedtech.com \
    --cc=joel@jms.id.au \
    --cc=leetroy@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@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).