From: Leif Lindholm <leif.lindholm@i3micro.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] "Problem in increasing initrd(RAMDISK) size"
Date: Wed, 08 Jun 2005 14:14:14 +0200 [thread overview]
Message-ID: <42A6E116.7090906@i3micro.com> (raw)
In-Reply-To: <20050608095309.7F725C1512@atlas.denx.de>
Wolfgang Denk wrote:
>>There is a hard limitation in u-boot, causing "bootm" command to
>>silently fail gunzip with images having an uncompressed size of > 4Mb.
>
> This has NOTHING to do with ramdisk sizes.
>
> U-Boot does not uncompress ramdisk images, this is done by the Linux
> kernel. U-Boot just (loads and) passes the address of the ramdisk
> image to the Linux kernel without touching the data at all.
>
>>The ugly fix would be to just increase this value (like I did).
>
> No such change is needed (unless you end up with a Linux kernel that
> does not fit in 4 MB any more).
Well, this is probably true in more sane cases, but when using embedded
ramdisk image (available for both mips and ppc I believe), the 4Mb
u-boot limit can indeed cause problems.
Yes I know everyone's supposed to upgrade to 2.6 and initramfs.
/
Leif
next prev parent reply other threads:[~2005-06-08 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 7:00 [U-Boot-Users] "Problem in increasing initrd(RAMDISK) size" nreddy at netenrich.com
2005-06-08 8:14 ` Wolfgang Denk
2005-06-08 9:00 ` Leif Lindholm
2005-06-08 9:53 ` Wolfgang Denk
2005-06-08 12:14 ` Leif Lindholm [this message]
2005-06-08 13:00 ` Wolfgang Denk
2005-06-08 13:49 ` Leif Lindholm
2005-06-08 14:32 ` Wolfgang Denk
2005-06-10 8:55 ` Leif Lindholm
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=42A6E116.7090906@i3micro.com \
--to=leif.lindholm@i3micro.com \
--cc=u-boot@lists.denx.de \
/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.