On 03/15/2012 04:10 PM, Rob Herring wrote: > On 03/15/2012 03:29 PM, Marek Vasut wrote: >> 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 <marek.va...@gmail.com> >>>>>> >>>>>> 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 ;-) >> > > They weren't in the original email header, only in the commit log as Cc's. > >>> How about: >>> >>> bootz <kern addr> [<fdt addr> [<initrd addr> [<initrd size>]]] >> >> What about bootz <kern addr> <initrd addr>[:<initrd size>] <fdt addr> >> >> example: bootz 0x12000000 0x13000000:0x40000 0x14000000 >> > > Sure. That works for me. > >>> >>> 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. > > Yes, but you already have to be aware of some commands which will change > env vars. This has to be script-able to be useful. The only other way I > see is adding a command to get the size of a file. Perhaps the ls > commands when given a single file can do that.
Turns out there is already a filesize variable that gets set on file load commands. And RTFM didn't help as that one is not documented... ;) Rob _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
