From: Wolfgang Denk <wd@denx.de>
To: Kent Borg <kentborg@borg.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Large initrd and arch/ppc/boot/simple Question
Date: Tue, 01 Jul 2003 22:38:17 +0200 [thread overview]
Message-ID: <20030701203822.DB949C592A@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 01 Jul 2003 16:29:44 EDT." <20030701162944.E20876@borg.org>
Dear Kent,
in message <20030701162944.E20876@borg.org> you wrote:
>
> We are booting our kernel via the arch/ppc/boot/simple mechanism to
> package up our kernel and initrd. It seems to work, until we get too
> big. What is big? Roughly 8 MB for our one big uncompressed userland
> program, plus the kernel, bash, busybox, and various userland
> utilities.
>
> Can initrd's get that large and still work? Is the simple boot code
> sensible with these sizes? (I notice that the "avail ram" message
> that gets printed is just hard coded number...)
I don't know about the "simple boot code". With U-Boot, we're
successfully using ramdisk images which uncompress into 128 MB and
bigger filesystems. [And no, please don't ask me who needs that many
stuff in a ramdisk, nor if there is not any better way to do this.]
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
A rolling stone gathers momentum.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-01 20:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 20:29 Large initrd and arch/ppc/boot/simple Question Kent Borg
2003-07-01 20:38 ` Wolfgang Denk [this message]
2003-07-01 21:51 ` Kent Borg
2003-07-01 22:07 ` Mark Hatle
2003-07-02 16:54 ` Kent Borg
2003-07-01 22:12 ` Tom Rini
2003-07-01 22:19 ` Kent Borg
-- strict thread matches above, loose matches on Subject: below --
2003-07-01 20:34 Kerl, John
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=20030701203822.DB949C592A@atlas.denx.de \
--to=wd@denx.de \
--cc=kentborg@borg.org \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).