linux-mips
[Top] [All Lists]

Re: Ramdisk image on flash.

To: linux-mips@linux-mips.org
Subject: Re: Ramdisk image on flash.
From: Guido Guenther <agx@sigxcpu.org>
Date: Thu, 20 Feb 2003 22:08:59 +0100
In-reply-to: <20030220123732.F7466@mvista.com>
Mail-followup-to: Guido Guenther <agx@sigxcpu.org>, linux-mips@linux-mips.org
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <200302201135.09154.krishnakumar@naturesoft.net> <1045765647.30379.262.camel@zeus.mvista.com> <3E552CDF.ECD08EEF@freehandsystems.com> <20030220194115.2A21378A6D@deneb.localdomain> <3E55342D.6E1D36FF@freehandsystems.com> <20030220123732.F7466@mvista.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4i
On Thu, Feb 20, 2003 at 12:37:32PM -0800, Jun Sun wrote:
> 1) create kernel ELF as normal
> 2) outside the kernel, create .o file that is ramfs root
> 3) outside the kernel, we use a separate tool/program that combines
>    1) and 2) into a new ELF file.  The entry point of the new ELF file
>    would append ramfs parameters (such as "initrd=xxxx") to the args
>    and then jump to kernel_entry.
This is basically what we do for IP22 in debian. We embed kernel and
initrd together with a small loader into one ELF executable. The prom
tftboots and starts the loader. The loader then moves the kernel to it's
loadaddres, puts the initrd to an appropriate address and jumps into
the kernel passing all the necessary args.
 -- Guido

<Prev in Thread] Current Thread [Next in Thread>