From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Matt Mackall <mpm@selenic.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] inflate pt1: refactor boot-time inflate code
Date: Fri, 24 Feb 2006 20:56:26 +0000 [thread overview]
Message-ID: <20060224205626.GB28855@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1.399206195@selenic.com>
On Fri, Feb 24, 2006 at 02:12:15PM -0600, Matt Mackall wrote:
> This is a refactored version of the lib/inflate.c:
>
> - clean up some really ugly code
> - clean up atrocities like '#include "../../../lib/inflate.c"'
> - drop a ton of cut and paste code from the kernel boot
> - move towards making the boot decompressor pluggable
> - move towards unifying the multiple inflate implementations
> - save space
>
> I'm sending this out in three batches. This first batch is core
> clean-ups without arch-specific changes.
>
> (This work was sponsored in part by the CE Linux Forum.)
ISTR something like this was posted months back, but I don't remember
what the status of it was. Hence, I might be repeating myself in this
reply, but I feel it's better to mention this than not to.
There's a comment at the top of arch/arm/boot/compressed/misc.c which
describes the use of the inflate code on ARM - for the kernel it's a
special case where the decompressor is run from ROM.
There's also another twist to it though - our relocatable zImage
requires us to build all files in the executable part of zImage
without _any_ static variables. If there's one or more static
variables, this feature breaks horribly (and silently in the non-
relocated cases.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-02-24 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 20:12 Matt Mackall
2006-02-24 20:56 ` Russell King [this message]
2006-02-24 21:30 ` Matt Mackall
2006-02-24 22:14 ` Nicolas Pitre
2006-02-24 22:07 ` Nicolas Pitre
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=20060224205626.GB28855@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome