From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: isar-users@googlegroups.com
Cc: henning.schild@siemens.com, adriaan.schmidt@siemens.com,
amikan@ilbers.de, ibr@ilbers.de, jan.kiszka@siemens.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH v4 0/2] use xz and gzip on host (outside chroot)
Date: Wed, 14 Sep 2022 22:21:16 +0200 [thread overview]
Message-ID: <20220914202118.168231-1-felix.moessbauer@siemens.com> (raw)
Changes since v3:
- add test for CROSS=1 wic image including compression
- integrate patch 2 into this series instead of standalone.
Please note, this series supersedes the "add wic.xz image to default qemuarm64 target" series
but does only requires little more disk space for the CI tests (compared to ISAR-next).
By that, the CI can still be executed on standard machines.
Changes since v1/v2:
instead of switching the compression logic, this patch adds support to run the whole imager in the buildchroot-host.
Felix Moessbauer (2):
run imager in buildchroot-host on cross
add wic.xz image to qemuarm64-bookworm
doc/user_manual.md | 11 +++++++++++
meta-isar/conf/multiconfig/qemuarm64-bookworm.conf | 3 +++
meta/classes/image-tools-extension.bbclass | 3 ---
testsuite/citest.py | 1 +
4 files changed, 15 insertions(+), 3 deletions(-)
--
2.30.2
next reply other threads:[~2022-09-14 20:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 20:21 Felix Moessbauer [this message]
2022-09-14 20:21 ` [PATCH v4 1/2] run imager in buildchroot-host on cross Felix Moessbauer
2022-09-15 9:14 ` Anton Mikanovich
2022-09-15 9:35 ` Moessbauer, Felix
2022-09-15 10:45 ` Anton Mikanovich
2022-09-15 11:04 ` Moessbauer, Felix
2022-09-15 11:06 ` Henning Schild
2022-09-15 15:43 ` Anton Mikanovich
2022-09-15 11:08 ` Henning Schild
2022-09-15 15:44 ` Anton Mikanovich
2022-09-15 17:08 ` Moessbauer, Felix
2022-09-16 7:41 ` Anton Mikanovich
2022-09-14 20:21 ` [PATCH v4 2/2] add wic.xz image to qemuarm64-bookworm Felix Moessbauer
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=20220914202118.168231-1-felix.moessbauer@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=amikan@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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