From: Zhihang Wei <wzh@ilbers.de>
To: Anton Mikanovich <amikan@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v2 00/11] Add new targets and required fixes
Date: Fri, 10 Jul 2026 11:18:13 +0200 [thread overview]
Message-ID: <86fc4a2e-f88e-4758-9625-e2ba0a541ae9@ilbers.de> (raw)
In-Reply-To: <20260629094624.855927-1-amikan@ilbers.de>
Applied to next, thanks.
Zhihang
On 6/29/26 11:46, Anton Mikanovich wrote:
> After trying to add Debian Forky and Ubuntu Resolute targets and cover them
> under CI it turns out there are some issues in both Isar and testsuite need to
> be fixed to make those targets work. This patchset accomulates target updates,
> fixes needed and also includes some test coverage cleanups which includes
> placing Debian Trixie RISCV64 QEMU target under CI testing.
>
> Known issues:
> ARM64 target of Ubuntu Resolute was moved to UEFI and startvm test case is
> currently not working, so it is covered under KFAIL until it will be fixed.
>
> Anton Mikanovich (11):
> grub: Remove obsolete efi_uga module for new distros
> CI: Freeze setuptools package version for avocado compatibility
> CI: Fix errors reporting during startvm
> meta: Add base distro overrides
> linux-kernel: Reverse linux-libc-dev package arch selection logic
> trixie: Split missing drivers hook recipes
> CI: Move trixie targets to generic test cases
> CI: Run startvm for all qemu targets
> meta: Add Ubuntu 26.04 (Resolute Raccoon) support
> testsuite: Cover Debian Trixie RISCV64 QEMU target with CI
> testsuite: Cover Debian Forky with CI
>
> kas/distro/Kconfig | 10 +-
> kas/distro/ubuntu-resolute.yaml | 9 +
> kas/machine/Kconfig | 4 +
> meta-isar/conf/distro/ubuntu-common.inc | 6 +-
> .../conf/distro/ubuntu-resolute-ports.list | 6 +
> meta-isar/conf/distro/ubuntu-resolute.conf | 14 +
> meta-isar/conf/distro/ubuntu-resolute.list | 6 +
> meta-isar/conf/machine/qemuarm64.conf | 8 +-
> meta-isar/conf/machine/qemuriscv64.conf | 3 +-
> meta-isar/conf/mc.conf | 5 +
> .../conf/multiconfig/bananapi-trixie.conf | 7 +-
> .../conf/multiconfig/nanopi-neo-trixie.conf | 8 +-
> .../conf/multiconfig/qemuamd64-forky.conf | 7 +
> .../conf/multiconfig/qemuamd64-resolute.conf | 7 +
> .../conf/multiconfig/qemuarm-trixie.conf | 3 +-
> .../conf/multiconfig/qemuarm64-forky.conf | 7 +
> .../conf/multiconfig/qemuarm64-resolute.conf | 7 +
> .../multiconfig/qemuriscv64-resolute.conf | 7 +
> ...hook_0.1.bb => initramfs-missing-hook.inc} | 6 +-
> .../initramfs-sunxi-mmc-hook_0.2.bb | 8 +
> .../initramfs-virtio-blk-hook_0.2.bb | 8 +
> meta/classes-recipe/linux-kernel.bbclass | 8 +-
> meta/conf/bitbake.conf | 2 +-
> .../wic/plugins/source/bootimg-efi-isar.py | 17 +-
> .../plugins/source/isoimage-isohybrid-isar.py | 23 +-
> scripts/ci_build.sh | 1 +
> testsuite/cibuilder.py | 40 ++-
> testsuite/citest.py | 261 +++++++++++++++---
> testsuite/data/targets.yml | 10 +
> testsuite/start_vm.py | 5 +-
> 30 files changed, 428 insertions(+), 85 deletions(-)
> create mode 100644 kas/distro/ubuntu-resolute.yaml
> create mode 100644 meta-isar/conf/distro/ubuntu-resolute-ports.list
> create mode 100644 meta-isar/conf/distro/ubuntu-resolute.conf
> create mode 100644 meta-isar/conf/distro/ubuntu-resolute.list
> create mode 100644 meta-isar/conf/multiconfig/qemuamd64-forky.conf
> create mode 100644 meta-isar/conf/multiconfig/qemuamd64-resolute.conf
> create mode 100644 meta-isar/conf/multiconfig/qemuarm64-forky.conf
> create mode 100644 meta-isar/conf/multiconfig/qemuarm64-resolute.conf
> create mode 100644 meta-isar/conf/multiconfig/qemuriscv64-resolute.conf
> rename meta-isar/recipes-initramfs/initramfs-trixie-armhf-hook/{initramfs-trixie-armhf-hook_0.1.bb => initramfs-missing-hook.inc} (92%)
> create mode 100644 meta-isar/recipes-initramfs/initramfs-trixie-armhf-hook/initramfs-sunxi-mmc-hook_0.2.bb
> create mode 100644 meta-isar/recipes-initramfs/initramfs-trixie-armhf-hook/initramfs-virtio-blk-hook_0.2.bb
>
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/86fc4a2e-f88e-4758-9625-e2ba0a541ae9%40ilbers.de.
prev parent reply other threads:[~2026-07-10 9:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 9:46 Anton Mikanovich
2026-06-29 9:46 ` [PATCH v2 01/11] grub: Remove obsolete efi_uga module for new distros Anton Mikanovich
2026-06-29 9:46 ` [PATCH v2 02/11] CI: Freeze setuptools package version for avocado compatibility Anton Mikanovich
2026-06-29 9:46 ` [PATCH v2 03/11] CI: Fix errors reporting during startvm Anton Mikanovich
2026-06-29 9:46 ` [PATCH v2 04/11] meta: Add base distro overrides Anton Mikanovich
2026-06-29 9:46 ` [PATCH v2 05/11] linux-kernel: Reverse linux-libc-dev package arch selection logic Anton Mikanovich
2026-06-29 9:46 ` [PATCH v2 06/11] trixie: Split missing drivers hook recipes Anton Mikanovich
2026-06-29 9:46 ` [PATCH v2 07/11] CI: Move trixie targets to generic test cases Anton Mikanovich
2026-06-29 9:46 ` [PATCH v2 08/11] CI: Run startvm for all qemu targets Anton Mikanovich
2026-06-29 9:46 ` [PATCH v2 09/11] meta: Add Ubuntu 26.04 (Resolute Raccoon) support Anton Mikanovich
2026-06-29 9:46 ` [PATCH v2 10/11] testsuite: Cover Debian Trixie RISCV64 QEMU target with CI Anton Mikanovich
2026-06-29 9:46 ` [PATCH v2 11/11] testsuite: Cover Debian Forky " Anton Mikanovich
2026-07-10 9:18 ` Zhihang Wei [this message]
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=86fc4a2e-f88e-4758-9625-e2ba0a541ae9@ilbers.de \
--to=wzh@ilbers.de \
--cc=amikan@ilbers.de \
--cc=isar-users@googlegroups.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