linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: andy@warmcat.com (Andy Green)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH needed?] ARM: add missing HAVE_KERNEL_GZIP
Date: Mon, 28 Sep 2009 09:19:14 +0100	[thread overview]
Message-ID: <4AC07182.90901@warmcat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0909280954490.4212@axis700.grange>

On 09/28/2009 08:56 AM, Somebody in the thread at some point said:
> On Mon, 28 Sep 2009, Uwe Kleine-K?nig wrote:
>
>> Hi Guennadi,
>>
>> On Mon, Sep 28, 2009 at 09:21:35AM +0200, Guennadi Liakhovetski wrote:
>>> Kernel fails to uncompress itself and boot without this patch.
>> I have no problem booting yesterday's linus/master without that change.
>>
>> What is the exact problem you see?
>
> Don't remember the error message exactly - something like "cannot
> uncompress" or "missing decompressor"... Observed on a i.MX31 system,
> although, if the problem were real, it probably would be present on all
> ARMs - none defines any of those decompressors. Will have to double-check
> then.

Just a comment on this, I run on an iMX device with an uncompressed 
kernel for a nice decrease in early boot time.  The kernel comes in at 
3MB uncompressed and the Qi bootloader I used pulls that in around half 
a second from uSD.

I use gzip for something else as it happens, but in the uncompressed 
case, boot is not dependent on gzip in the kernel.

-Andy

      reply	other threads:[~2009-09-28  8:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28  7:21 [PATCH needed?] ARM: add missing HAVE_KERNEL_GZIP Guennadi Liakhovetski
2009-09-28  7:53 ` Uwe Kleine-König
2009-09-28  7:56   ` Guennadi Liakhovetski
2009-09-28  8:19     ` Andy Green [this message]

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=4AC07182.90901@warmcat.com \
    --to=andy@warmcat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).