From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Date: Fri, 04 May 2007 11:02:53 -0500 Subject: [U-Boot-Users] [PATCH v3] Fix initrd length miscalculation in bootm command when using a dtu In-Reply-To: <463B4191.1000706@smiths-aerospace.com> References: <20070504082836.4C04C353AF1@atlas.denx.de> <463B3463.1030702@freescale.com> <200705041546.13452.sr@denx.de> <463B4191.1000706@smiths-aerospace.com> Message-ID: <463B592D.4040600@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Jerry Van Baren wrote: > but I don't understand how to build an image with all three pieces in it > (I tried to use the ":" in the -d source parameter and mkimage just got > confused, couldn't find the files). Am I expecting too much??? Should > I just be wrapping the three pieces individually and loading them > separately? What exactly are you doing to test this, Timur? The 'len' bug only shows up if both of these conditions are met: 1) You're booting an OF-enabled kernel (i.e. there's an fdt) 2) The fdt is wrapped in a dtu image (type IH_TYPE_FLATDT) I didn't test having the fdt merged in with other entities in a combined image. I just made a dtu and told the bootm command to use it. So if you want to test this code, I think just wrapping the three pieces individually should be sufficient. Part of the problem is that the code looks for a dtu image. If you combine all three chunks into one image, then I don't know what the code will do, because the image type won't be IH_TYPE_FLATDT. -- Timur Tabi Linux Kernel Developer @ Freescale