From: Dave Littell <littelld@verizon.net>
To: linuxppc-embedded@ozlabs.org
Subject: Re: initramfs too large?
Date: Wed, 10 Sep 2008 20:49:08 -0500 [thread overview]
Message-ID: <48C87914.4000005@verizon.net> (raw)
In-Reply-To: <48C7CD29.7040906@coritel.it>
Marco Stornelli wrote:
> Hi Dave,
>
> no if well remeber for 2.6.18 it's "ramdisk_size" (before this option
> had a name slightly different) but you can check it out in the kernel
> documentation (in the documentation folder of your kernel). Another
> thing: you should check out that the kernel, the initram disk and the
> dtb are loaded in ram from your bootloader without overlapping, maybe
> you've changed the dimensions and something is overlapped.
>
Everything is included in one zImage, so where things are placed in
memory is all a function of the linker, wrapper, and gunzip, right? I
did try a "ramdisk_size" command-line argument and saw no change in
behavior.
I noticed today that with the smaller initramfs the kernel is smaller
than 8 MB (_end < 0xc0800000), but with the larger initramfs all the
symbols following the end marker for initramfs are beyond 8 MB. Is this
a clue?
Using the JTAG I stopped at early_init() and looked at the
__machine_desc_start area. I noticed that when booting with the smaller
initramfs there's (apparently) good information in there but with the
larger initramfs the area is mostly filled with 0xff's. I'm now
wondering if there's some relationship between this 8 MB boundary and
possibly some problem in the zImage wrapper, the wrapper's gunzip, or
something in that area.
So, is 8 MB some magic number for the PowerPC kernel?
Thanks,
Dave
prev parent reply other threads:[~2008-09-11 1:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 0:50 initramfs too large? Dave Littell
2008-09-10 6:36 ` Marco Stornelli
2008-09-10 12:20 ` Dave Littell
2008-09-10 13:35 ` Marco Stornelli
2008-09-11 1:49 ` Dave Littell [this message]
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=48C87914.4000005@verizon.net \
--to=littelld@verizon.net \
--cc=linuxppc-embedded@ozlabs.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).