From: Kumba <kumba@gentoo.org>
To: linux-mips <linux-mips@linux-mips.org>
Cc: zhuzhenhua <zzh.hust@gmail.com>
Subject: Re: how to emdedded ramdisk.gz in vmlinux for linux-2.6.14?
Date: Tue, 17 Jan 2006 20:10:00 -0500 [thread overview]
Message-ID: <43CD9568.1000707@gentoo.org> (raw)
In-Reply-To: <1137515220.11738.2.camel@localhost.localdomain>
Marc Karasek wrote:
> Is this a better solution than having the ramdisk embedded?
This is embedding the ramdisk. Only in a different way.
> It seems that most of the MIPS development is embedded designs and this
> could be a problem if it is not :
>
> 1) Easier
Not exactly easier, initially. I spent near a few weeks figuring initramfs out.
The kernel is rather picky on certain things. The main point is you need
/init, and if it's a script, then the very first line must be a hashbang
(!#/bin/blah). Those two gave me headaches for awhile. Other oddities can
occur that make initramfs a bit of a pain initially.
> or
> 2) Faster
Faster by what? initramfs is unique because it resides on a level above the
arches, so it tends to be a sort of universal ramdisk. SGI Origin system
couldn't use ramdisks originally because of their memory structure. They can,
however, use initramfs. I maintained patches for a time (up until ~2.6.13) that
added embedded ramdisk support back into the kernel, but now that I have
initramfs down pretty well (a tool does the grunt work for my needs, actually),
I'm not going to maintain those patches any longer.
--Kumba
--
Gentoo/MIPS Team Lead
Gentoo Foundation Board of Trustees
"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:[~2006-01-18 1:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 14:48 how to emdedded ramdisk.gz in vmlinux for linux-2.6.14? Marc Karasek
2006-01-17 0:26 ` Kumba
2006-01-17 16:27 ` Marc Karasek
2006-01-18 1:10 ` Kumba [this message]
2006-01-19 21:07 ` Marc Karasek
2006-01-19 22:49 ` Stuart Longland
2006-01-20 4:11 ` Kumba
2006-01-20 18:43 ` Marc Karasek
2006-01-20 19:02 ` Marc Karasek
2006-01-20 19:02 ` Marc Karasek
2006-01-20 19:08 ` Stephen P. Becker
[not found] ` <200601202129.11398.p_christ@hol.gr>
[not found] ` <1137786593.22994.46.camel@localhost.localdomain>
[not found] ` <200601202203.14325.p_christ@hol.gr>
2006-01-20 20:47 ` Marc Karasek
2006-01-20 21:02 ` P. Christeas
2006-01-20 21:03 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2006-01-20 21:27 Marc Karasek
2006-01-20 21:27 ` Marc Karasek
2006-01-15 4:22 zhuzhenhua
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=43CD9568.1000707@gentoo.org \
--to=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=zzh.hust@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.