From: Bruno Thomsen <bth@kamstrup.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Cc: Bruno Thomsen <bth@kamstrup.com>
Subject: [ptxdist] Generation of additional xz rootfs archive
Date: Wed, 11 Nov 2015 14:06:36 +0000 [thread overview]
Message-ID: <915054555B5659448ACF8A70E114824D01FAA1C7E2@Exchange2010.kamstrup.dk> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1028 bytes --]
Hi,
I am currently looking into the possibility of adding ptxdist generation of
a xz rootfs archive, as I thought the feature might be useful for others as
well.
Should it be added as a new script like ptxd_make_image_archive_impl
(image/archive) or implemented in C inside genimage (image/genimage)?
The goal is to optimize our firmware upgrade image size.
This could be done by switching from gz to xz rootfs which reduces size with
approx 35%.
The production firmware will still be using a gz rootfs archive.
I basically want to do the following command:
gzip -d < root.tgz | xz -9e > root.tar.xz
Compression level should be configurable so it can be adjusted to target
memory size.
Memory usage is approx 65MB during extraction of a -9 archive on an i.MX28
processor when using xz from Busybox.
In my testing the CompMem/DecMem listed in "man xz" seems to be valid for
embedded ARM Linux systems as well.
Otherwise this will just end as even more clutter in our custom build script
wrapper around ptxdist :)
/Bruno
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3540 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2015-11-11 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 14:06 Bruno Thomsen [this message]
2015-11-18 17:42 ` Michael Olbrich
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=915054555B5659448ACF8A70E114824D01FAA1C7E2@Exchange2010.kamstrup.dk \
--to=bth@kamstrup.com \
--cc=ptxdist@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