Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Pete Popov <ppopov@mvista.com>
Cc: Jun Sun <jsun@mvista.com>,
	Tibor Polgar <tpolgar@freehandsystems.com>,
	Mark Salter <msalter@redhat.com>,
	krishnakumar@naturesoft.net, linux-mips@linux-mips.org
Subject: Re: Ramdisk image on flash.
Date: Thu, 20 Feb 2003 16:24:40 -0500	[thread overview]
Message-ID: <3E554798.5060403@embeddededge.com> (raw)
In-Reply-To: 1045774664.16543.307.camel@zeus.mvista.com

Pete Popov wrote:

> Me too. Keep in mind too that there is no "standard" zImage support in
> mips right now.  I'm not sure what Dan is using for the zImage support,

I took what you had started, copied lots of stuff from the same thing
I did for PowerPC a long time ago, and actually improved on that (I think) :-).
It seems every Alchemy processor I work with has a different boot rom,
so like PowerPC this gives us the ability to also format kernel calling
conventions in addition to zImage/initrd booting and flexibility.

> that but that's another patch that needs to make its way in the source
> tree.

I'll get it there :-)

> ....  I added zImage support in the form of an arch/mips/zboot
> directory and supporting files, but that never made it in linux-mips.org
> because it added yet another copy of zlib (my argument was, so what, all
> the other arches do it).

Yeah, I know about zlib.  I have "fixed" this more than once on PowerPC
to use the kernel zlib, but it still hasn't stuck in the source tree :-)
I'll try to get it right when I do a MIPS patch.

Thanks.


	-- Dan

  reply	other threads:[~2003-02-20 21:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20  6:05 Ramdisk image on flash Krishnakumar. R
2003-02-20 18:27 ` Pete Popov
2003-02-20 19:30   ` Tibor Polgar
2003-02-20 19:41     ` Mark Salter
2003-02-20 20:01       ` Tibor Polgar
2003-02-20 20:16         ` Mark Salter
2003-02-20 20:35         ` Dan Malek
2003-02-20 20:44           ` Jun Sun
2003-02-20 20:57             ` Pete Popov
2003-02-20 21:24               ` Dan Malek [this message]
2003-02-20 20:37         ` Jun Sun
2003-02-20 21:08           ` Guido Guenther
2003-02-20 21:12         ` Alan Cox
2003-02-20 19:41     ` Pete Popov
2003-02-20 19:42     ` Brian Murphy
2003-02-20 20:59   ` Guido Guenther
2003-02-20 21:27     ` Dan Malek
2003-02-21  2:24 ` Atsushi Nemoto
2003-02-21 20:25   ` fixup_bigphys_addr and DBAu1500 dev board Jeff Baitis
2003-02-21 20:40     ` Dan Malek
2003-02-21 22:10       ` Pete Popov
2003-02-22  3:50       ` Jeff Baitis
2003-02-23  9:19         ` Geert Uytterhoeven
2003-02-24 17:46         ` Pete Popov
2003-02-25 21:54           ` Jeff Baitis
2003-02-25 22:05             ` Pete Popov

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=3E554798.5060403@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=jsun@mvista.com \
    --cc=krishnakumar@naturesoft.net \
    --cc=linux-mips@linux-mips.org \
    --cc=msalter@redhat.com \
    --cc=ppopov@mvista.com \
    --cc=tpolgar@freehandsystems.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