From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Vasut Date: Thu, 15 Mar 2012 21:29:33 +0100 Subject: [U-Boot] [PATCH V6] BOOT: Add "bootz" command to boot Linux zImage on ARM In-Reply-To: <4F62479F.8070509@gmail.com> References: <201203152005.03198.marex@denx.de> <4F62479F.8070509@gmail.com> Message-ID: <201203152129.33296.marex@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Rob Herring, > 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? > You lost some people in the Cc ;-) > How about: > > bootz [ [ []]] What about bootz [:] example: bootz 0x12000000 0x13000000:0x40000 0x14000000 > > 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. If you load kernel after initrd, that's screw things up. > > 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. Naw, this is weird. What do you think about my idea with the addr:size stuff? > > Rob Best regards, Marek Vasut