All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael-lists@free-electrons.com>
To: Florian Fainelli <florian@openwrt.org>
Cc: Mike Rapoport <mike@compulab.co.il>, Alain Knaff <alain@knaff.lu>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	linux-embedded mailing list <linux-embedded@vger.kernel.org>
Subject: Re: Status of bzip2 and lzma kernel compression for ARM?
Date: Thu, 25 Jun 2009 17:24:59 +0200	[thread overview]
Message-ID: <4A4396CB.9000703@free-electrons.com> (raw)
In-Reply-To: <200906251104.02830.florian@openwrt.org>

On 06/25/2009 11:04 AM, Florian Fainelli wrote:
> Le Thursday 25 June 2009 10:56:45 Mike Rapoport, vous avez écrit :
>> I'm not sure what exactly do you mean by "test bzip2 and lzma compression
>> on ARM", but if you refer to internal initramfs compression, I can tell
>> that I've used lzma compression on PXA270 and it works fine.
>>     
>
> I think Michael refers to the lzma decompressor which allows you to use a 
> lzma-compressed kernel as a (b)zImage with its architecture specific 
> decompressor piggy-backed in the (b)zImage.
>
> Such thing would also be very useful on MIPS and PowerPC as well.
>   
Yes, that's what I meant: using a bzip2 or lzma compressed kernel. I
would like to know the boot time impact on an ARM board.

If I don't get any answer from Alain in the next days, I will propose a
patch update for ARM.

Cheers,

Michael.

-- 
Michael Opdenacker, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2009-06-25 15:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 20:22 Status of bzip2 and lzma kernel compression for ARM? Michael Opdenacker
2009-06-24 20:22 ` Michael Opdenacker
2009-06-25  8:56 ` Mike Rapoport
2009-06-25  9:04   ` Florian Fainelli
2009-06-25 15:24     ` Michael Opdenacker [this message]
2009-06-25 17:08       ` Paul Mundt
2009-06-28 13:57       ` Alain Knaff
2009-06-28 14:47         ` Alain Knaff
2009-06-29 12:21           ` Mike Rapoport
2009-06-29 16:39             ` Michael Opdenacker
2009-07-03 15:43             ` Albin Tonnerre
2009-07-03 15:43               ` Albin Tonnerre
2009-07-13 19:17               ` Albin Tonnerre
  -- strict thread matches above, loose matches on Subject: below --
2009-11-11 16:34 Martin Michlmayr
2009-11-11 17:07 ` Albin Tonnerre
2009-11-11 17:20   ` Martin Michlmayr
2009-11-12  8:45     ` Alain Knaff

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=4A4396CB.9000703@free-electrons.com \
    --to=michael-lists@free-electrons.com \
    --cc=alain@knaff.lu \
    --cc=florian@openwrt.org \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mike@compulab.co.il \
    --cc=thomas.petazzoni@free-electrons.com \
    /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.