From: "Cédric Le Goater" <clg@kaod.org>
To: Alexander Hansen <alexander.hansen@9elements.com>, qemu-devel@nongnu.org
Cc: Titus Rwantare <titusr@google.com>,
Peter Maydell <peter.maydell@linaro.org>,
Steven Lee <steven_lee@aspeedtech.com>,
Troy Lee <leetroy@gmail.com>,
Jamin Lin <jamin_lin@aspeedtech.com>,
Kane Chen <kane_chen@aspeedtech.com>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Joel Stanley <joel@jms.id.au>,
qemu-arm@nongnu.org
Subject: Re: [PATCH v3 2/5] ast2600: yosemite4 functional test
Date: Tue, 12 May 2026 18:34:35 +0200 [thread overview]
Message-ID: <e9828347-20a8-49ec-be2d-e9f9a1f7c7c1@kaod.org> (raw)
In-Reply-To: <20260512102157.176511-3-alexander.hansen@9elements.com>
On 5/12/26 12:20, Alexander Hansen wrote:
> Tested: functional test passed.
>
> export QEMU_TEST_QEMU_BINARY=qemu-system-arm
> ./build/run tests/functional/arm/test_aspeed_fby4.py
> TAP version 13
> ok 1 test_aspeed_fby4.YosemiteV4Machine.test_arm_ast2600_yosemitev4_openbmc
> 1..1
The above is not useful information for the reader, developer,
maintainer.
As a commit log, we generally provide some info on what is the test,
what the test does, where the FW images come from, what is excluded
if so, etc.
Something like :
Add a functional test for the Yosemite V4 (fby4-bmc) machine
that validates:
- U-Boot initialization and kernel boot sequence
The test uses an OpenBMC image built for the yosemite4 board and
validates console output through the boot process.
The rest looks good. I like adding network but this is up to you.
Thanks,
C.
> Cc: Titus Rwantare <titusr@google.com>
> Cc: "Cédric Le Goater" <clg@kaod.org> (maintainer:ASPEED BMCs)
> Cc: Peter Maydell <peter.maydell@linaro.org> (maintainer:ASPEED BMCs)
> Cc: Steven Lee <steven_lee@aspeedtech.com> (reviewer:ASPEED BMCs)
> Cc: Troy Lee <leetroy@gmail.com> (reviewer:ASPEED BMCs)
> Cc: Jamin Lin <jamin_lin@aspeedtech.com> (reviewer:ASPEED BMCs)
> Cc: Kane Chen <kane_chen@aspeedtech.com> (reviewer:ASPEED BMCs)
> Cc: Andrew Jeffery <andrew@codeconstruct.com.au> (reviewer:ASPEED BMCs)
> Cc: Joel Stanley <joel@jms.id.au> (reviewer:ASPEED BMCs)
> Cc: qemu-arm@nongnu.org (open list:ASPEED BMCs)
> Cc: qemu-devel@nongnu.org (open list:All patches CC here)
> Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>
> ---
> tests/functional/arm/meson.build | 2 ++
> tests/functional/arm/test_aspeed_fby4.py | 44 ++++++++++++++++++++++++
> 2 files changed, 46 insertions(+)
> create mode 100755 tests/functional/arm/test_aspeed_fby4.py
>
> diff --git a/tests/functional/arm/meson.build b/tests/functional/arm/meson.build
> index 2f538f29a2..10c0006f22 100644
> --- a/tests/functional/arm/meson.build
> +++ b/tests/functional/arm/meson.build
> @@ -14,6 +14,7 @@ test_arm_timeouts = {
> 'aspeed_ast2600_sdk_otp' : 720,
> 'aspeed_bletchley' : 480,
> 'aspeed_catalina' : 480,
> + 'aspeed_fby4': 480,
> 'aspeed_gb200nvl_bmc' : 480,
> 'aspeed_rainier' : 480,
> 'bpim2u' : 500,
> @@ -47,6 +48,7 @@ tests_arm_system_thorough = [
> 'aspeed_ast2600_sdk_otp',
> 'aspeed_bletchley',
> 'aspeed_catalina',
> + 'aspeed_fby4',
> 'aspeed_gb200nvl_bmc',
> 'aspeed_rainier',
> 'bpim2u',
> diff --git a/tests/functional/arm/test_aspeed_fby4.py b/tests/functional/arm/test_aspeed_fby4.py
> new file mode 100755
> index 0000000000..a3124c240f
> --- /dev/null
> +++ b/tests/functional/arm/test_aspeed_fby4.py
> @@ -0,0 +1,44 @@
> +#!/usr/bin/env python3
> +#
> +# Functional test that boots the ASPEED machines
> +#
> +# SPDX-License-Identifier: GPL-2.0-or-later
> +
> +from qemu_test import Asset
> +from aspeed import AspeedTest
> +
> +
> +class YosemiteV4Machine(AspeedTest):
> +
> + ASSET_YOSEMITE_V4_FLASH = Asset(
> + 'https://github.com/legoater/qemu-aspeed-boot/raw/refs/heads/master/images/yosemite4-bmc/openbmc-20260505132843/obmc-phosphor-image-yosemite4-20260505132843.static.mtd.xz',
> + 'dff6946363b41f952b15cfc3156482b89fcfc1b0ecfc3ec8b3ed496a5f001ef9')
> +
> + def do_test_arm_aspeed_openbmc_no_network(self, machine, image, uboot,
> + cpu_id, soc):
> +
> + self.set_machine(machine)
> + self.vm.set_console()
> + self.vm.add_args('-drive', f'file={image},if=mtd,format=raw',
> + '-snapshot')
> + self.vm.launch()
> +
> + self.wait_for_console_pattern(f'U-Boot {uboot}')
> + self.wait_for_console_pattern('## Loading kernel from FIT Image')
> + self.wait_for_console_pattern('Starting kernel ...')
> + self.wait_for_console_pattern(f'Booting Linux on physical CPU {cpu_id}')
> + self.wait_for_console_pattern(f'ASPEED {soc}')
> + self.wait_for_console_pattern('/init as init process')
> + # yosemite v4 does not emit the hostname log which is
> + # different from the other machines.
> + self.wait_for_console_pattern('yosemite4 login:')
> +
> + def test_arm_ast2600_yosemitev4_openbmc(self):
> + image_path = self.uncompress(self.ASSET_YOSEMITE_V4_FLASH)
> +
> + self.do_test_arm_aspeed_openbmc_no_network('fby4-bmc', image=image_path,
> + uboot='2019.04', cpu_id='0xf00',
> + soc='AST2600 rev A3')
> +
> +if __name__ == '__main__':
> + AspeedTest.main()
next prev parent reply other threads:[~2026-05-12 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 10:20 [PATCH v3 0/5] initial support for yosemite v4 Alexander Hansen
2026-05-12 10:20 ` [PATCH v3 1/5] ast2600: yosemite4 initial support Alexander Hansen
2026-05-12 16:13 ` Cédric Le Goater
2026-05-12 10:20 ` [PATCH v3 2/5] ast2600: yosemite4 functional test Alexander Hansen
2026-05-12 16:34 ` Cédric Le Goater [this message]
2026-05-12 10:20 ` [PATCH v3 3/5] hw/sensor: MAX31790 support Alexander Hansen
2026-05-12 16:51 ` Cédric Le Goater
2026-05-12 10:20 ` [PATCH v3 4/5] hw/sensor: support MAX11615 Alexander Hansen
2026-05-12 16:55 ` Cédric Le Goater
2026-05-12 16:58 ` Cédric Le Goater
2026-05-12 10:20 ` [PATCH v3 5/5] hw/sensor: support Texas Instruments ADC128D818 Alexander Hansen
2026-05-12 16:57 ` 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=e9828347-20a8-49ec-be2d-e9f9a1f7c7c1@kaod.org \
--to=clg@kaod.org \
--cc=alexander.hansen@9elements.com \
--cc=andrew@codeconstruct.com.au \
--cc=jamin_lin@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=kane_chen@aspeedtech.com \
--cc=leetroy@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=steven_lee@aspeedtech.com \
--cc=titusr@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.