DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: distrokit@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [DistroKit] [PATCH v5 6/7] image-rauc: use ext4 rootfs instead of tar.gz
Date: Fri, 25 Aug 2023 13:03:09 +0200	[thread overview]
Message-ID: <20230825110310.2948272-7-rhi@pengutronix.de> (raw)
In-Reply-To: <20230825110310.2948272-1-rhi@pengutronix.de>

On one hand, the squashfs inside the RAUC bundle already uses
compression, so with a tar.gz inside a squashfs the content is
compressed twice. Also using ext4 makes it possible to use adaptive
updates in the future.

(Yes, the image generated by the image-root-ext recipe is really called
"root.ext2", even if it's an ext4 image.)

Link: https://rauc.readthedocs.io/en/latest/advanced.html#adaptive-updates
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
 config/images/rauc.config    | 4 ++--
 platforms/image-rauc.deps.in | 6 ++++++
 2 files changed, 8 insertions(+), 2 deletions(-)
 create mode 100644 platforms/image-rauc.deps.in

diff --git a/config/images/rauc.config b/config/images/rauc.config
index e4169cc8cd95..83e074274961 100644
--- a/config/images/rauc.config
+++ b/config/images/rauc.config
@@ -1,6 +1,6 @@
 image @IMAGE@ {
 	rauc {
-		file root.tar.gz { image = "root.tgz" }
+		file root.ext4 { image = "root.ext2" }
 		manifest = "
 			[update]
 			compatible=@RAUC_BUNDLE_COMPATIBLE@
@@ -12,7 +12,7 @@ image @IMAGE@ {
 			format=@RAUC_BUNDLE_FORMAT@
 
 			[image.rootfs]
-			filename=root.tar.gz
+			filename=root.ext4
 			"
 		cert = "@RAUC_CERT@"
 		key = "@RAUC_KEY@"
diff --git a/platforms/image-rauc.deps.in b/platforms/image-rauc.deps.in
new file mode 100644
index 000000000000..2b2853441a96
--- /dev/null
+++ b/platforms/image-rauc.deps.in
@@ -0,0 +1,6 @@
+## SECTION=image
+
+config IMAGE_RAUC
+	tristate
+	select IMAGE_ROOT_EXT
+	select IMAGE_ROOT_EXT_EXT4
-- 
2.39.2




  parent reply	other threads:[~2023-08-25 11:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 11:03 [DistroKit] [PATCH v5 0/7] v7a: add redundant update support via RAUC Roland Hieber
2023-08-25 11:03 ` [DistroKit] [PATCH v5 1/7] enable MTD and UBI tools Roland Hieber
2023-08-25 11:06   ` Alexander Dahl
2023-08-25 12:19     ` [DistroKit] [PATCH] fixup! " Roland Hieber
2023-08-25 13:04   ` [DistroKit] [PATCH v5 1/7] " Robert Schwebel
2023-08-25 11:03 ` [DistroKit] [PATCH v5 2/7] rauc: add initial support Roland Hieber
2023-08-25 13:04   ` Robert Schwebel
2023-08-25 11:03 ` [DistroKit] [PATCH v5 3/7] silence QA checks regarding missing kernel features for RAUC Roland Hieber
2023-08-25 13:05   ` Robert Schwebel
2023-08-25 11:03 ` [DistroKit] [PATCH v5 4/7] v7a: enable RAUC bundle creation Roland Hieber
2023-08-25 13:08   ` Robert Schwebel
2023-08-28  9:00     ` Roland Hieber
2023-08-25 11:03 ` [DistroKit] [PATCH v5 5/7] image-rauc: fork config file from PTXdist 2023.08.0 Roland Hieber
2023-08-25 13:06   ` Robert Schwebel
2023-08-25 11:03 ` Roland Hieber [this message]
2023-08-25 13:09   ` [DistroKit] [PATCH v5 6/7] image-rauc: use ext4 rootfs instead of tar.gz Robert Schwebel
2023-08-25 11:03 ` [DistroKit] [PATCH v5 7/7] v7a: run: start with barebox by default Roland Hieber
2023-08-25 13:09   ` Robert Schwebel

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=20230825110310.2948272-7-rhi@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=distrokit@pengutronix.de \
    /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