From mboxrd@z Thu Jan  1 00:00:00 1970
From: Leif Lindholm <leif.lindholm@i3micro.com>
Date: Wed, 08 Jun 2005 14:14:14 +0200
Subject: [U-Boot-Users] "Problem in increasing initrd(RAMDISK) size"
In-Reply-To: <20050608095309.7F725C1512@atlas.denx.de>
References: <20050608095309.7F725C1512@atlas.denx.de>
Message-ID: <42A6E116.7090906@i3micro.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.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