From: "Linh Dang" <linhd@nortelnetworks.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: "Embedded Linux PPC list" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: list of 2.6-related migration issues for embedded programmers?
Date: Mon, 19 Jul 2004 21:29:38 -0400 [thread overview]
Message-ID: <wn54qo3a2kd.fsf@linhd-2.ca.nortel.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0407191558120.24452@dell.enoriver.com> (Robert P. J. Day's message of "Mon, 19 Jul 2004 16:01:08 -0400")
On 19 Jul 2004, rpjday@mindspring.com wrote:
[...]
>
> and all i need to change is "ramdisk.image.gz" to, say, my "newc"
> format gzipped cpio archive, "initramfs.cpio.gz", and the early
> kernel code should recognize it as such automatically?
>
> i'll give that a shot later.
>
> rday
look at populate_rootfs(), it's that simple. Our local kernel tree has
the following in the boot/simple/Makefile:
ZRDIMAGE := $(images)/ramdisk.image.gz
ROOTDIR := $(srctree)/............/path/to/dir/containing/root-fs
$(ZRDIMAGE) : $(OUR_LOCAL_RULES_FOR_BUSYBOX) FORCE
(cd $(ROOTDIR) && find | grep -v '~$$' | cpio -o -Hnewc ) | \
gzip -9 -c > $@
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-20 1:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 12:15 list of 2.6-related migration issues for embedded programmers? Robert P. J. Day
2004-07-19 17:32 ` Linh Dang
2004-07-19 17:51 ` Robert P. J. Day
2004-07-19 18:14 ` Linh Dang
2004-07-19 19:06 ` Robert P. J. Day
2004-07-19 20:01 ` Robert P. J. Day
2004-07-20 1:29 ` Linh Dang [this message]
2004-07-19 20:58 ` Wolfgang Denk
2004-07-19 21:34 ` Robert P. J. Day
2004-07-19 22:04 ` Wolfgang Denk
2004-07-19 22:12 ` Robert P. J. Day
2004-07-20 1:38 ` Linh Dang
2004-07-20 7:16 ` Wolfgang Denk
2004-07-20 11:29 ` Linh Dang
2004-07-20 12:32 ` Robert P. J. Day
2004-07-20 13:19 ` Linh Dang
2004-07-20 12:40 ` Mark Chambers
2004-07-20 13:42 ` Wolfgang Denk
2004-07-20 16:07 ` Linh Dang
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=wn54qo3a2kd.fsf@linhd-2.ca.nortel.com \
--to=linhd@nortelnetworks.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rpjday@mindspring.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.