From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Subject: [isar-cip-core][PATCH v2 0/6] Add support for EROFS
Date: Tue, 5 Nov 2024 18:54:27 +0100 [thread overview]
Message-ID: <cover.1730829273.git.jan.kiszka@siemens.com> (raw)
Changes in v2:
- update cip-kernel-config revision further to support non-x86 qemu targets
EROFS is a read-only file system that can act as alternative to squashfs
that we so far use for our A/B OTA update setups. It can perform faster
during runtime but may come with larger storage demand. See [1] for some
comparison.
We just enabled support for it in our 6.1 defconfigs, and this series now
enable CIP core to switch from squashfs to EROFS when requested.
Jan
[1] https://sigma-star.at/blog/2022/07/squashfs-erofs
Jan Kiszka (6):
Make the read-only rootfs type configurable
initramfs-crypt-hook: Prepare for EROFS as alternative
Add initramfs-erofs-hook
Introduce class for generating EROFS images
linux-cip: Update cip-kernel-config revision
kas: Add option for selecting read-only rootfs type
Kconfig | 16 +++++++++
classes/erofs.bbclass | 34 +++++++++++++++++++
classes/swupdate.bbclass | 3 +-
classes/verity.bbclass | 2 +-
conf/distro/cip-core-common.inc | 4 ++-
conf/layer.conf | 2 +-
kas/opt/erofs.yml | 16 +++++++++
kas/opt/swupdate.yml | 8 ++---
.../files/encrypt_partition.script | 2 +-
...ook_0.2.bb => initramfs-crypt-hook_0.3.bb} | 0
.../initramfs-erofs-hook/files/erofs.hook | 25 ++++++++++++++
.../initramfs-erofs-hook_0.1.bb | 24 +++++++++++++
recipes-kernel/linux/cip-kernel-config.inc | 2 +-
wic/bbb-efibootguard.wks.in | 2 +-
wic/hihope-rzg2m-efibootguard.wks.in | 2 +-
wic/qemu-arm64-efibootguard.wks.in | 2 +-
wic/qemu-riscv64-efibootguard.wks.in | 2 +-
wic/x86-uefi-efibootguard.wks.in | 2 +-
18 files changed, 133 insertions(+), 15 deletions(-)
create mode 100644 classes/erofs.bbclass
create mode 100644 kas/opt/erofs.yml
rename recipes-initramfs/initramfs-crypt-hook/{initramfs-crypt-hook_0.2.bb => initramfs-crypt-hook_0.3.bb} (100%)
create mode 100644 recipes-initramfs/initramfs-erofs-hook/files/erofs.hook
create mode 100644 recipes-initramfs/initramfs-erofs-hook/initramfs-erofs-hook_0.1.bb
--
2.43.0
next reply other threads:[~2024-11-05 17:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 17:54 Jan Kiszka [this message]
2024-11-05 17:54 ` [isar-cip-core][PATCH v2 1/6] Make the read-only rootfs type configurable Jan Kiszka
2024-11-05 17:54 ` [isar-cip-core][PATCH v2 2/6] initramfs-crypt-hook: Prepare for EROFS as alternative Jan Kiszka
2024-11-05 17:54 ` [isar-cip-core][PATCH v2 3/6] Add initramfs-erofs-hook Jan Kiszka
2024-11-05 17:54 ` [isar-cip-core][PATCH v2 4/6] Introduce class for generating EROFS images Jan Kiszka
2024-11-05 17:54 ` [isar-cip-core][PATCH v2 5/6] linux-cip: Update cip-kernel-config revision Jan Kiszka
2024-11-05 17:54 ` [isar-cip-core][PATCH v2 6/6] kas: Add option for selecting read-only rootfs type Jan Kiszka
2024-11-07 6:31 ` [isar-cip-core][PATCH v3 " Jan Kiszka
2024-11-15 5:55 ` Gao Xiang
2024-11-15 7:01 ` Jan Kiszka
2024-11-15 7:18 ` Gao Xiang
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=cover.1730829273.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cip-dev@lists.cip-project.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