Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Jon Burgess" <Jon_Burgess@eur.3com.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: EV64120 anybody?
Date: Fri, 8 Nov 2002 14:52:25 +0000	[thread overview]
Message-ID: <80256C6B.0051C5D4.00@notesmta.eur.3com.com> (raw)



Ralf wrote:
> Does anybody still care about support for the EV64120?
> It's significant time since I last received a report about
> this board.  As it is at least the code in
> arch/mips/galileo-boards/ev64120/compressed is in a shape
> such that I cannot merge it with Linus, so that means
> either somebody who cares about this board is going
> to clean the code or I'm considering to do the rm -rf
> thing ...

I copied the approach in ev64120/compressed to implement a
compressed kernel in a product based on a different chip. Having
a compressed kernel image is fairly crucial for use in an
embedded system.

I think this is the only example of support for a compressed
kernel image in the linux-mips.org code. There was the start of
some more generic support in the SF tree but I haven't
looked at it recently.

Is the problem that the code is not generic, or are there some
other issues?

I cleaned up the code a bit to get it compile with the latest
tools when I copied it, but it is still not generic enough.

The misc.c #include "../../../../../lib/inflate.c' is a nasty
piece of coding.

     Jon

             reply	other threads:[~2002-11-08 14:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-08 14:52 Jon Burgess [this message]
2002-11-08 15:17 ` EV64120 anybody? Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2002-11-08 13:06 Ralf Baechle

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=80256C6B.0051C5D4.00@notesmta.eur.3com.com \
    --to=jon_burgess@eur.3com.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@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