From: "Cédric Le Goater" <clg@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org,
"Peter Maydell" <peter.maydell@linaro.org>,
"Joel Stanley" <joel@jms.id.au>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v2] aspeed: Deprecate the tacoma-bmc machine
Date: Mon, 26 Aug 2024 11:58:55 +0200 [thread overview]
Message-ID: <5fb7342b-fa67-4cb2-b6fd-2241b7b76d03@redhat.com> (raw)
In-Reply-To: <4e04f930-e7af-4084-99a8-2a3139e2bf43@roeck-us.net>
Hello Guenter,
On 8/9/24 00:05, Guenter Roeck wrote:
> Hi,
>
> On Tue, Jun 25, 2024 at 09:08:30AM +0200, Cédric Le Goater wrote:
>> The tacoma-bmc machine was a board including an AST2600 SoC based BMC
>> and a witherspoon like OpenPOWER system. It was used for bring up of
>> the AST2600 SoC in labs. It can be easily replaced by the rainier-bmc
>> machine which is part of a real product offering.
>>
>> Signed-off-by: Cédric Le Goater <clg@redhat.com>
>
> I have been using tacoma-bmc to test tcg,tpm-tis-i2c functionality
> on arm. rainier-bmc doesn't support that, and other IBM BMCs which
> do support it (bonnell, everest, system1) are not supported in qemu.
>
> Do you have a suggested alternative ?
Could you use the ast2600-evb machine instead ? as done in
machine_aspeed.py, see routine test_arm_ast2600_evb_buildroot_tpm.
We can't add a "tpm-tis-i2c" device to the tacoma-bmc machine init
routine because a TPM backend is required.
Thanks,
C.
next prev parent reply other threads:[~2024-08-26 10:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 7:08 [PATCH v2] aspeed: Deprecate the tacoma-bmc machine Cédric Le Goater
2024-06-25 7:12 ` Philippe Mathieu-Daudé
2024-07-02 5:56 ` Cédric Le Goater
2024-08-08 22:05 ` Guenter Roeck
2024-08-26 9:58 ` Cédric Le Goater [this message]
2024-08-26 18:50 ` Guenter Roeck
2024-08-28 12:35 ` Cédric Le Goater
2024-08-28 15:12 ` Guenter Roeck
2024-08-30 8:09 ` Cédric Le Goater
2024-08-30 20:11 ` Guenter Roeck
2024-09-09 11:20 ` Joel Stanley
2024-09-09 15:10 ` Guenter Roeck
2024-09-11 17:33 ` Cédric Le Goater
2024-09-11 18:18 ` Guenter Roeck
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=5fb7342b-fa67-4cb2-b6fd-2241b7b76d03@redhat.com \
--to=clg@redhat.com \
--cc=andrew@codeconstruct.com.au \
--cc=joel@jms.id.au \
--cc=linux@roeck-us.net \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).