From: Ralf Baechle <ralf@linux-mips.org>
To: Dan Malek <dan@embeddededge.com>
Cc: Colin.Helliwell@Zarlink.Com, linux-mips@linux-mips.org
Subject: Re: Compressed kernels
Date: Thu, 20 Nov 2003 22:02:57 +0100 [thread overview]
Message-ID: <20031120210257.GA758@linux-mips.org> (raw)
In-Reply-To: <3FBCDBF7.7000307@embeddededge.com>
On Thu, Nov 20, 2003 at 10:21:27AM -0500, Dan Malek wrote:
> Date: Thu, 20 Nov 2003 10:21:27 -0500
> From: Dan Malek <dan@embeddededge.com>
> To: Colin.Helliwell@Zarlink.Com
> CC: linux-mips@linux-mips.org
> Subject: Re: Compressed kernels
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Colin.Helliwell@Zarlink.Com wrote:
>
> >I'm running a 2.4.21 kernel tree, and would like to have kernel
> >compression. I wondered if this has gone back into the latest versions yet?
>
> If you apply the 'zImage' patch from Pete's ftp directory (look in past
> e-mails for this discussion) you will see what I have done for a few of
> the boards I'm using. It's quite trivial to add new boards to get
> this feature. I'm still working on the method of attaching the
> compressed initrd to the same image, which I find quite useful for
> embedded applications.
Compressed kernels seem to be fairly high on everybody's list. Due to
size limits of some boatloaders and flash memory being always too small
and too expensive I guess there would also be some interest in bzip2
support.
Ralf
next prev parent reply other threads:[~2003-11-20 21:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 9:10 Compressed kernels Colin.Helliwell
2003-11-20 15:21 ` Dan Malek
2003-11-20 21:02 ` Ralf Baechle [this message]
2003-11-20 21:42 ` Dan Malek
2003-11-20 22:33 ` Wolfgang Denk
2003-11-20 22:50 ` Dan Malek
2003-11-25 23:44 ` Ralf Baechle
2003-11-22 2:41 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2005-03-31 8:35 Compressed Kernels JP Foster
2005-03-31 8:42 ` Robin H. Johnson
2005-03-31 16:24 ` Pete Popov
2005-04-01 9:05 ` JP
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=20031120210257.GA758@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Colin.Helliwell@Zarlink.Com \
--cc=dan@embeddededge.com \
--cc=linux-mips@linux-mips.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