From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] initramfs: add support for LZO and XZ compression methods
Date: Tue, 22 Jan 2013 18:05:54 +0100 [thread overview]
Message-ID: <20130122180554.6c540102@skate> (raw)
In-Reply-To: <1358808943-17063-3-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Mon, 21 Jan 2013 19:55:43 -0300, Gustavo Zacarias wrote:
> +config BR2_TARGET_ROOTFS_CPIO_LZO
> + bool "lzo"
> + help
> + Do compress the cpio filesystem with lzo.
> +
> +config BR2_TARGET_ROOTFS_CPIO_XZ
> + bool "xz"
> + help
> + Do compress the cpio filesystem with xz.
I don't remember exactly, but isn't the kernel build process itself
capable of compressing the initramfs already? I remember we had some
discussion about this a while ago, but I don't remember the outcome of
these. Arnout was leading this discussion, IIRC.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-22 17:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 22:55 [Buildroot] [PATCH 1/3] lzop: add LZOP definition for the host variant Gustavo Zacarias
2013-01-21 22:55 ` [Buildroot] [PATCH 2/3] xz: add XZ " Gustavo Zacarias
2013-01-21 22:55 ` [Buildroot] [PATCH 3/3] initramfs: add support for LZO and XZ compression methods Gustavo Zacarias
2013-01-21 23:38 ` Stefan Fröberg
2013-01-21 23:44 ` Gustavo Zacarias
2013-01-22 0:34 ` Stefan Fröberg
2013-01-22 17:05 ` Thomas Petazzoni [this message]
2013-01-22 18:17 ` Stefan Fröberg
2013-01-24 7:11 ` Arnout Vandecappelle
2013-01-24 11:55 ` Stefan Fröberg
2013-01-24 10:48 ` Gustavo Zacarias
2013-01-24 12:08 ` Stefan Fröberg
2013-01-24 12:13 ` Gustavo Zacarias
2013-01-24 7:09 ` Arnout Vandecappelle
2013-01-24 10:57 ` Gustavo Zacarias
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=20130122180554.6c540102@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.