From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] initramfs: add support for LZO and XZ compression methods
Date: Mon, 21 Jan 2013 20:44:28 -0300 [thread overview]
Message-ID: <50FDD2DC.8050004@zacarias.com.ar> (raw)
In-Reply-To: <50FDD171.60804@petroprogram.com>
On 01/21/2013 08:38 PM, Stefan Fr?berg wrote:
> You will probably need --check=crc32 with that xz-compression.
> I have had difficulties booting linux 3.3.1 kernel (don't know about
> later versions)
> with xz-compressed initramfs without that option.
You are 100% correct.
It didn't fail me during testing because buildroot is never using any
compressed cpio archive, thus the previous options (gzip, bzip2) were
never used.
I noticed when checking the bzImage size in a tweaked qemu_x86_defconfig
test run that it never changed much.
New patchset will follow that fixes this and the previous issue.
Regards.
next prev parent reply other threads:[~2013-01-21 23:44 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 [this message]
2013-01-22 0:34 ` Stefan Fröberg
2013-01-22 17:05 ` Thomas Petazzoni
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=50FDD2DC.8050004@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox