mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Generation of additional xz rootfs archive
Date: Wed, 18 Nov 2015 18:42:45 +0100	[thread overview]
Message-ID: <20151118174245.GE28802@pengutronix.de> (raw)
In-Reply-To: <915054555B5659448ACF8A70E114824D01FAA1C7E2@Exchange2010.kamstrup.dk>

Hi,

On Wed, Nov 11, 2015 at 02:06:36PM +0000, Bruno Thomsen wrote:
> 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 :)

This can be easily done in PTXdist. You just need to use the 'new' image
mechanism:

$ ptxdist newpackage image-genimage

 - remove the .config file
 - select IMAGE_ROOT_TGZ in the .in file and remove select for genimage.
 - remove the _FILES and __CONFIG line the .make file
 - replace the image/genimage line with your recompression command.

We cannot define every possible image within upstream PTXdist. That's why I
created the new image mechanism to make it easy to add new images in a BSP.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2015-11-18 17:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 14:06 Bruno Thomsen
2015-11-18 17:42 ` Michael Olbrich [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=20151118174245.GE28802@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --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