Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Geoffrey Espin <espin@idiom.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, 4 Mar 2002 15:19:31 -0800	[thread overview]
Message-ID: <20020304151931.B9117@idiom.com> (raw)
In-Reply-To: <20020304145709.A1332@oss.sgi.com>; from Ralf Baechle on Mon, Mar 04, 2002 at 02:57:09PM -0800

On Mon, Mar 04, 2002 at 02:57:09PM -0800, Ralf Baechle wrote:
>                                                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 :-)

Do you mean just the 'ad hoc' MIPS schemes, or across the whole gamut of
Linux architectures?

The problem isn't so much the compression mechanics, but the BSP/LSP.

It would be helpful if there was one architecture that was
considered the 'ideal'.  Though I haven't actually used it:
arch/ppc/boot appears very flexible, and adheres to a strict
layout and naming convention.

Geoff
--
Geoffrey Espin
espin@idiom.com

      parent reply	other threads:[~2002-03-05  0:19 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
2002-03-04 23:35       ` Geoffrey Espin
2002-03-04 23:19   ` Geoffrey Espin [this message]

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=20020304151931.B9117@idiom.com \
    --to=espin@idiom.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