linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: alexander.stein@systec-electronic.com (Alexander Stein)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: add support for uncompressed uImage kernel
Date: Thu, 18 Nov 2010 11:18:45 +0100	[thread overview]
Message-ID: <201011181118.45476.alexander.stein@systec-electronic.com> (raw)
In-Reply-To: <20101118091046.GA16907@n2100.arm.linux.org.uk>

Hello,

On Thursday 18 November 2010, 10:10:46 Russell King - ARM Linux wrote:
> On Thu, Nov 18, 2010 at 08:38:26AM +0100, Alexander Stein wrote:
> > We only have experience with GZIP. Our compressed kernel is ~1,8MB and
> > uncompressed ~4MB.
> > On an AT91 ARM9 SoC the decompression takes about 1-2s of time. Caches
> > should be disabled, as far as I could see in decompression code.
> 
> Are you sure?  ARM9 is supposed to be ARMv4T, which is covered by this
> entry in the proc_types table:
> 
>                 .word   0x00020000              @ ARMv4T
>                 .word   0x000f0000
>                 W(b)    __armv4_mmu_cache_on
>                 W(b)    __armv4_mmu_cache_off
>                 W(b)    __armv4_mmu_cache_flush
> 
> So caches _should_ be enabled.

I'm _not_ sure. That was a long time ago and I only did a short look into the 
decompression/setup code.
After I noticed using the uncompressed kernel is much faster, I didn't 
investigate further.

Best regards,
Alexander

  reply	other threads:[~2010-11-18 10:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 13:50 [PATCH] ARM: add support for uncompressed uImage kernel Alexander Stein
2010-11-09 14:04 ` Russell King - ARM Linux
2010-11-09 14:51   ` Uwe Kleine-König
2010-11-09 22:38   ` Sascha Hauer
2010-11-13 10:47   ` Albin Tonnerre
2010-11-18  7:38     ` Alexander Stein
2010-11-18  8:15       ` Uwe Kleine-König
2010-11-18  9:10       ` Russell King - ARM Linux
2010-11-18 10:18         ` Alexander Stein [this message]
2010-11-09 14:57 ` Uwe Kleine-König

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=201011181118.45476.alexander.stein@systec-electronic.com \
    --to=alexander.stein@systec-electronic.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).