Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Tibor Polgar <tpolgar@freehandsystems.com>
To: Pete Popov <ppopov@mvista.com>
Cc: krishnakumar@naturesoft.net, linux-mips@linux-mips.org
Subject: Re: Ramdisk image on flash.
Date: Thu, 20 Feb 2003 11:30:39 -0800	[thread overview]
Message-ID: <3E552CDF.ECD08EEF@freehandsystems.com> (raw)
In-Reply-To: 1045765647.30379.262.camel@zeus.mvista.com

Pete Popov wrote:
> 
> On Wed, 2003-02-19 at 22:05, Krishnakumar. R wrote:
> > Hi,
> >
> > Is there any way that I can keep
> > a ramdisk image (containing the root filesystem)
> > in a flash device and boot to it.
> 
> Yes, and other architectures have support for passing arguments to the
> kernel that tell it where the ramdisk is. I don't know that we've done
> that for MIPS, yet.  It wouldn't be too hard to do and maybe someone on
> this list is already working on it (I think someone actually is working
> on it and was preparing a patch for Ralf).

For having separate initrd and kernel load we also need an aware bootloader
that knows where to find the ramdisk.   RedBoot, from what i read, seems to be
i386 specific.    The Yamon i've patched "COULD" be made to do it.   

> 
> > The ramdisk should be separate from the kernel image.

How is this currently done in non-mips archs?   I know lilo and Druid can do
this with a configuration file and hard sector addressing into a filesystem,
but i never understood how they avoid/get around file fragmentation issues.

Tibor

  reply	other threads:[~2003-02-20 19:30 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 [this message]
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
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=3E552CDF.ECD08EEF@freehandsystems.com \
    --to=tpolgar@freehandsystems.com \
    --cc=krishnakumar@naturesoft.net \
    --cc=linux-mips@linux-mips.org \
    --cc=ppopov@mvista.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