From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: Romain Naour <romain.naour@smile.fr>,
Bin Meng <bmeng@tinylab.org>,
Alistair Francis <alistair.francis@wdc.com>,
Jan-Benedict Glaw <jbglaw@lug-owl.de>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 10/10] board/sifive: hifive-unleashed: Include QEMU instructions in readme.txt
Date: Sat, 12 Aug 2023 23:14:27 +0200 [thread overview]
Message-ID: <20230812231427.7dee9cbb@windsurf> (raw)
In-Reply-To: <20230626160030.93063-11-bmeng.cn@gmail.com>
Hello,
+Romain Naour in Cc.
On Tue, 27 Jun 2023 00:00:30 +0800
Bin Meng <bmeng.cn@gmail.com> wrote:
> From: Bin Meng <bmeng@tinylab.org>
>
> The upstream QEMU 'sifive_u' machine supports running upstream U-Boot
> for the SiFive HiFive Unleashed board out of the box.
>
> Add the QEMU instructions for testing in readme.txt.
>
> Signed-off-by: Bin Meng <bmeng@tinylab.org>
> ---
Applied to next, thanks.
Now that this defconfig can be booted under Qemu, maybe it makes sense
to ensure that our Gitlab CI does some actual testing of the
"bootability" of this image under Qemu? Could you have a look at how
our qemu_* defconfigs do this, and try to adapt the HiFive Unleashed
defconfig to do the same? Romain Naour in Cc is the author/maintainer
of this logic that all the testing of Qemu defconfigs in our CI, so I'm
sure he can provide guidance if needed.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-12 21:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 16:00 [Buildroot] [PATCH 00/10] riscv: Various fixes and small enhancements Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 01/10] configs/hifive_unleashed: Update to use OpenSBI 1.2 Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 02/10] configs/hifive_unleashed: Update to use U-Boot v2023.04 Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 03/10] configs/hifive_unleashed: Enable BR2_RISCV_ISA_CUSTOM_RVA explicitly Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 04/10] configs/beaglev_defconfig: " Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 05/10] arch/Config.in.riscv: Remove BR2_RISCV_ISA_CUSTOM_RVA from BR2_riscv_custom Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 06/10] configs: riscv: Drop BR2_TARGET_OPENSBI_CUSTOM_VERSION Bin Meng
2023-06-26 17:10 ` Yann E. MORIN
2023-06-27 2:11 ` Bin Meng
2023-06-27 20:39 ` Yann E. MORIN
2023-06-26 16:00 ` [Buildroot] [PATCH 07/10] boot/opensbi: Config.in: Cosmetic style fix Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 08/10] boot/opensbi: Bump to version 1.3 Bin Meng
2023-06-26 16:00 ` [Buildroot] [PATCH 09/10] board/sifive: hifive-unleashed: Update rootfs offset Bin Meng
2023-06-26 17:12 ` Yann E. MORIN
2023-08-12 21:12 ` Thomas Petazzoni via buildroot
2023-06-26 16:00 ` [Buildroot] [PATCH 10/10] board/sifive: hifive-unleashed: Include QEMU instructions in readme.txt Bin Meng
2023-06-26 17:21 ` Yann E. MORIN
2023-06-27 0:32 ` Alistair Francis
2023-06-28 15:15 ` Bin Meng
2023-08-12 21:14 ` Thomas Petazzoni via buildroot [this message]
2023-06-26 17:04 ` [Buildroot] [PATCH 00/10] riscv: Various fixes and small enhancements Yann E. MORIN
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=20230812231427.7dee9cbb@windsurf \
--to=buildroot@buildroot.org \
--cc=alistair.francis@wdc.com \
--cc=bmeng.cn@gmail.com \
--cc=bmeng@tinylab.org \
--cc=jbglaw@lug-owl.de \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.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