linux-mips
[Top] [All Lists]

Re: [PATCH]: Rewrite of arch/mips/ramdisk/

To: linux-mips@linux-mips.org
Subject: Re: [PATCH]: Rewrite of arch/mips/ramdisk/
From: Kumba <kumba@gentoo.org>
Date: Sun, 14 Nov 2004 12:25:15 -0500
In-reply-to: <20041114085202.GA30480@lst.de>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <4196FE7C.9040309@gentoo.org> <20041114085202.GA30480@lst.de>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla Thunderbird 0.9 (Windows/20041103)
Christoph Hellwig wrote:

So why do you keep it instead of using initramfs as you should - which
is the portable method useable on all ports.

Not sure I'm following what you're asking/referring to. This is for an embedded filesystem initrd, like for a small busybox-based initrd, useful for netboot images and the like. From looking at the initramfs stuff in usr/, that looks to be specific for linking config.gz into the kernel, and not configurable to link in a filesystem-based initrd.

I basically mimiced the method in usr/ for arch/mips/ramdisk/. If there's some more global mechanism for utilizing this and tying in an initrd, then I didn't see it. The current code in arch/mips/ramdisk/ is virtually the same as the stuff in arch/sh/ramdisk/, so it doesn't look like any kind of code sharing is going on between the various ports that have an optional embedded ramdisk.


--Kumba

--
"Such is oft the course of deeds that move the wheels of the world: small hands do them because they must, while the eyes of the great are elsewhere." --Elrond

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