Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5186] New: initramfs/cpio should support lzo compression
Date: Sun, 06 May 2012 14:46:37 +0200	[thread overview]
Message-ID: <4FA672AD.2030905@mind.be> (raw)
In-Reply-To: <bug-5186-163@https.bugs.busybox.net/>

On 05/05/12 17:13, bugzilla at busybox.net wrote:
> Created attachment 4340
>    -->  https://bugs.busybox.net/attachment.cgi?id=4340
> cpio lzo support
>
> Linux supports lzo compression for the initramfs image nowadays, so it would be
> nice if buildroot did as well
There should be a variable $(LZOP) and a dependency on host-lzop, just like for lzma.  lzop is not a package that you 
can expect to be available on the host.

  Regards,
  Arnout

  PS What's the policy for reacting to patches posted on bugzilla?

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
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

  reply	other threads:[~2012-05-06 12:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-05 15:13 [Buildroot] [Bug 5186] New: initramfs/cpio should support lzo compression bugzilla at busybox.net
2012-05-06 12:46 ` Arnout Vandecappelle [this message]
2012-05-07 13:54   ` Thomas Petazzoni
2012-05-11 20:43     ` Arnout Vandecappelle
2012-05-14 19:09       ` Peter Korsgaard
2013-05-04 14:21 ` [Buildroot] [Bug 5186] " bugzilla at busybox.net

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=4FA672AD.2030905@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox