From mboxrd@z Thu Jan  1 00:00:00 1970
From: Timur Tabi <timur@freescale.com>
Date: Tue, 20 Feb 2007 10:36:00 -0600
Subject: [U-Boot-Users] [PATCH] Fix initrd length miscalculation in
 bootm command
In-Reply-To: <8FD8ED2E-51F4-4DD1-97AD-02AD68A390AC@kernel.crashing.org>
References: <20070206004307.D7C18353AF8@atlas.denx.de>
	<45C89A99.8070709@freescale.com>
	<8FA84569-4397-4F6F-8781-F4EA6EC40139@kernel.crashing.org>
	<45C8B6D7.7050302@freescale.com>
	<37B7ABBF-458F-4B50-80D8-F3FE22A52EB2@kernel.crashing.org>
	<45DA37FB.3070804@freescale.com>
	<8FD8ED2E-51F4-4DD1-97AD-02AD68A390AC@kernel.crashing.org>
Message-ID: <45DB2370.6090804@freescale.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

Kumar Gala wrote:

> Sounds right, I'd double check that your rootfs.ext2.gz.uboot isn't 
> already a uImage, but the actual ext2 image gziped.

Yes, it is a uImage.  I guess I need to find the original now.

Also, I was wondering if 200000 is too low of a load address.  Doesn't the 
kernel lock that memory or something?

-- 
Timur Tabi
Linux Kernel Developer @ Freescale