[Top] [All Lists]

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

Subject: Re: [PATCH]: Rewrite of arch/mips/ramdisk/
From: Kumba <>
Date: Sun, 14 Nov 2004 14:31:18 -0500
In-reply-to: <>
Original-recipient: rfc822;
References: <> <> <>
User-agent: Mozilla Thunderbird 0.9 (Windows/20041103)
Kumba wrote:

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.

Ahh, I see. Ralf pointed me at CONFIG_INITRAMFS_SOURCE in 2.6.10. My patch was based on 2.6.9, and I didn't exactly think this specific bit of the kernel would change between 2.6.9 and 2.6.10. Go figure.

It looks like this option, which afaict, doesn't seem to have an entry anywhere in Kconfig, specifies a list of files for inclusion in a cpio archive that's bundled into the kernel. My question then is, can a lookback-mountable filesystem image be included in this list, and the kernel, given /dev/ram0 as root, know to mount and use the loopback image?


"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>