From: Jun Sun <jsun@mvista.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: William Jhun <wjhun@ayrnetworks.com>, linux-mips@oss.sgi.com
Subject: Re: Compressed images?
Date: Mon, 04 Mar 2002 14:50:43 -0800 [thread overview]
Message-ID: <3C83FA43.4090407@mvista.com> (raw)
In-Reply-To: 20020304145709.A1332@oss.sgi.com
Ralf Baechle wrote:
> On Mon, Mar 04, 2002 at 12:08:03PM -0800, William Jhun wrote:
>
>
>>I've been looking through the recent linux-mips archives and it seems
>>there isn't a concensus about where to build compressed ((b)zImage)
>>images. We have been placing our code under arch/mips/boot/compressed,
>>though it seems that the latest oss tree doesn't have such a directory,
>>and the only reference I can find to building a compressed image is in
>>galileo-boards/ev64120/compressed/.
>>
>>Should we be placing our boot image compression stuff in our
>>platform-specific directory? Are most MIPS-based Linux platforms not
>>using compressed images?
>>
>
> General rant, not directed to you personally. Right now we've got more
> than half a dozen variations of code to support compressed images throughout
> the kernel. So I'm not going to accept any new patches for compressed
> images before this mess has been cleaned. Volunteers :-)
>
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
next prev parent reply other threads:[~2002-03-04 23:50 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 [this message]
2002-03-04 23:03 ` William Jhun
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=3C83FA43.4090407@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.com \
--cc=wjhun@ayrnetworks.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