From: Stuart Longland <redhatter@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: how to emdedded ramdisk.gz in vmlinux for linux-2.6.14?
Date: Fri, 20 Jan 2006 08:49:41 +1000 [thread overview]
Message-ID: <43D01785.1090103@gentoo.org> (raw)
In-Reply-To: <1137704865.22994.7.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1818 bytes --]
Marc Karasek **top-posted**: (Reading emails bottom-to-top is no fun)
> Is the process still the same. In that you create a ramdisk image that
> can be mounted, just using initramfs instead?
>
> We will be moving to 2.6.x for our next chip and currently have scripts
> to create a ramdisk with busybox embedded. If these cannot be used
> anymore, I may want to take over the patches for ramdisk from you and
> maintain them. Otherwise our sdk would have to change and the tools,
> etc. and that is not a desireable option......
Initramfs works by generating a cpio archive of a directory, and
embedding a compressed version of that. This is unpacked at boot time,
into something similar to a tmpfs-like filesystem. It then starts /init
to bring the system online (identical to /linuxrc).
There's a couple of things you can do. One, is to simply adapt your
scripts to create a cpio archive directly, and then set INITRAMFS_SOURCE
to the full path to your cpio archive.
Alternatively, the kernel can create the cpio archive for you, simply
point INITRAMFS_SOURCE at the root directory. You can also use this
trick to import a initrd image into initramfs ... simply loop-mount the
initrd somewhere, then point INITRAMFS_SOURCE at the mountpoint. (Ohh,
and don't forget to `ln -s /linuxrc /init` in your image)
So yeah, there'll be modifications required ... but the changes should
be minimal. I'm guessing it'll possibly even simplify the tools -- as
you don't have to worry about `dd`ing a ramdisk image from /dev/zero,
running losetup, then formatting, mounting and transferring the filesystem.
--
Stuart Longland (aka Redhatter) .'''.
Gentoo Linux/MIPS Cobalt and Docs Developer '.'` :
. . . . . . . . . . . . . . . . . . . . . . .'.'
http://dev.gentoo.org/~redhatter :.'
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2006-01-19 22:46 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
2006-01-19 21:07 ` Marc Karasek
2006-01-19 22:49 ` Stuart Longland [this message]
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=43D01785.1090103@gentoo.org \
--to=redhatter@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