From: William Jhun <wjhun@ayrnetworks.com>
To: Jun Sun <jsun@mvista.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>, linux-mips@oss.sgi.com
Subject: Re: Compressed images?
Date: Mon, 4 Mar 2002 15:03:34 -0800 [thread overview]
Message-ID: <20020304150334.D1247@ayrnetworks.com> (raw)
In-Reply-To: <3C83FA43.4090407@mvista.com>; from jsun@mvista.com on Mon, Mar 04, 2002 at 02:50:43PM -0800
On Mon, Mar 04, 2002 at 02:50:43PM -0800, Jun Sun wrote:
>
> I think I am leaning towards leaving compressed image outside kernel itself.
>
> I don't see any technical reason why it must be inside kernel.
>
> Then it must be the code sharing argument. However, it seem MIPS boards are
> so much more diversified than x86 machines. Any sharing, if there are any, is
> limited. Also there are other way of sharing code than stacking it into
> kernle tree, I suppose.
>
> Another aimless general rant .... :-)
>
> Jun
But this is a good point. Our own compressed/ build requires building
several elf-header-mangling tools just to get our bootstrap (which we
can't change) to even recognize the finished image.
Though, I'm not sure how much the different decompression (misc.c)
routines vary; could there be some way to do this in a
platform-independent way?
Hmm!
Will
next prev parent reply other threads:[~2002-03-05 0:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 20:08 Compressed images? William Jhun
2002-03-04 21:31 ` Karsten Merker
2002-03-04 22:57 ` Ralf Baechle
2002-03-04 22:50 ` Jun Sun
2002-03-04 23:03 ` William Jhun [this message]
2002-03-04 23:35 ` Geoffrey Espin
2002-03-04 23:19 ` Geoffrey Espin
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=20020304150334.D1247@ayrnetworks.com \
--to=wjhun@ayrnetworks.com \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.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.