Kumar Gala wrote: [...]
Introducing routines for parsing new uImage format bootm arguments: [<addr>]#<conf> - configuration specification [<addr>]:<subimg> - subimage specification
New format images can contain multiple subimages of the same type. For example a single new format image file can contain three kernels, two ramdisks and a couple of FDT blobs. Subimage and configuration specifications are extensions to bootm (and other image-related commands) arguments' syntax that allow to specify which particular subimage should be operated on.
Subimage specification is used to denote a particular subimage. Configurations are a bit more complex -- they are used to define a particualr booting setup, for example a (kernel, fdt blob) pair, or a (kernel, ramdisk, fdt blob) tuple, etc.
Signed-off-by: Marian Balakowicz m8@semihalf.com
Mind adding a example of what <conf> and <subimg> would/could be set to. (Its not clear to me if these are indexes [0..n] or labels)
Both <conf> and <subimg> are unit names from the image source file (dts format) used to generate the image. For example, having an image generated using the source file with the following structure:
/{ images { kernel@1 { ... kernel@2 { ... ramdisk@1 { ... fdt@1 { ... fdt@2 { ... fdt@3 { ... };
configurations { conf@1 { ... }; };
one could in U-Boot do:
bootm 300000:kernel@1 bootm 300000:kernel@2 :ramdisk@1 :fdt@3 bootm 300000:kernel@2 - 300000:fdt@1 bootm 300000:config@1
This will be documented better in the form of a doc/README.<something> file that we plan to post. And I'd rather not add too much documentation to the commit log, especially now that Wolfgang has merged the patches to the new-image branch of u-boot-testing.
Regards, Bartlomiej