From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1 v2] build host lz4 to support lz4 compression in the kernel.
Date: Wed, 01 Apr 2015 23:55:01 +0200 [thread overview]
Message-ID: <551C6935.3050401@mind.be> (raw)
In-Reply-To: <20150401223752.0fd358cf@free-electrons.com>
On 01/04/15 22:37, Thomas Petazzoni wrote:
> Dear Sagaert Johan,
>
> On Wed, 1 Apr 2015 22:12:33 +0200, Sagaert Johan wrote:
>
>> +# lz4 kernel compression is only available on ARM and kernel >= 3.11
>> +# we always build host-lz4 when the target is ARM.
>> +# (how could i use LINUX_VERSION_PROBED to check for >=3.11 ?)
>> +ifeq ($(BR2_arm),y)
>> +LINUX_DEPENDENCIES += host-lz4
>> +endif
>
> No that still isn't good: LZ4 compressed kernel is available on ARM,
> MIPS, x86 and S390 (we don't care about the latter in Buildroot).
>
> No, I really think we need to add new options in linux/Config.in.
Well, I'm in agreement with Johan's earlier statement that the overhead of the
host-lz4 build is negligible. It takes 20 seconds on my laptop, of which 6 are
buildroot overhead from parsing package/*/*.mk.
Peter said before that all this hacking of linux (or other) config files should
be avoided, and I agree.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-04-01 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 20:12 [Buildroot] [PATCH 1/1 v2] build host lz4 to support lz4 compression in the kernel Sagaert Johan
2015-04-01 20:37 ` Thomas Petazzoni
2015-04-01 21:55 ` Arnout Vandecappelle [this message]
2015-04-01 22:01 ` Thomas Petazzoni
2015-04-02 22:06 ` Yann E. MORIN
2015-04-02 23:35 ` Johan Sagaert
2015-04-04 22:51 ` Johan Sagaert
2015-04-05 9:12 ` Yann E. MORIN
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=551C6935.3050401@mind.be \
--to=arnout@mind.be \
--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.