From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Date: Thu, 15 Mar 2012 14:48:47 -0500 Subject: [U-Boot] [PATCH V6] BOOT: Add "bootz" command to boot Linux zImage on ARM In-Reply-To: <201203152005.03198.marex@denx.de> References: <1331797965-7415-1-git-send-email-marex@denx.de> <4F623A42.9020602@gmail.com> <201203152005.03198.marex@denx.de> Message-ID: <4F62479F.8070509@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 03/15/2012 02:05 PM, Marek Vasut wrote: > Dear Rob Herring, > >> On 03/15/2012 02:52 AM, Marek Vasut wrote: >>> From: Marek Vasut >>> >>> This command boots Linux zImage from where the zImage is loaded to. >>> Passing initrd and fdt is supported. >> >> This is great! However, the initrd is still in the u-boot image format, >> right? >> >> If a raw initrd is supported, then we could get rid of flash-kernel on >> disk-based debian/ubuntu systems. The file size is known from the >> filesystem, but then needs to get to the bootz command somehow. > > Yes. Initrd still needs a bit of work, ideas? How about: bootz [ [ []]] I changed the order so the size can be optional without resorting to using a "-". Then no size means u-boot image format. File load commands would need to set loadsize env var. Another idea is to prepend the u-boot image header on file loading. This would need some way to disable the crc check and specify any other data. It would probably be hard to do without changing existing commands. Rob