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.vasut@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 ;-)
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
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