From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: [PATCH]: Rewrite of arch/mips/ramdisk/
Date: Sun, 14 Nov 2004 12:25:15 -0500 [thread overview]
Message-ID: <419794FB.6020104@gentoo.org> (raw)
In-Reply-To: <20041114085202.GA30480@lst.de>
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
next prev parent reply other threads:[~2004-11-14 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-14 6:43 [PATCH]: Rewrite of arch/mips/ramdisk/ Kumba
2004-11-14 8:52 ` Christoph Hellwig
2004-11-14 17:25 ` Kumba [this message]
2004-11-14 19:31 ` Kumba
2004-11-15 17:55 ` Ralf Baechle
2004-11-16 1:21 ` Kumba
2004-11-15 18:05 ` Christoph Hellwig
2004-11-17 13:17 ` Ralf Baechle
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=419794FB.6020104@gentoo.org \
--to=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
/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