From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bartlomiej Sieka <tur@semihalf.com>
Date: Fri, 22 Feb 2008 10:48:09 +0100
Subject: [U-Boot-Users] [PATCH 3/5] [new uImage] Add fit_parse_conf()
 and	fit_parse_subimage() routines
In-Reply-To: <F9E24F68-5094-4E7A-9165-27445608F70D@kernel.crashing.org>
References: <20080221175529.21243.64282.stgit@pollux.denx.de>
	<20080221175548.21243.16591.stgit@pollux.denx.de>
	<F9E24F68-5094-4E7A-9165-27445608F70D@kernel.crashing.org>
Message-ID: <47BE9A59.2090100@semihalf.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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 at 1 { ...
                 kernel at 2 { ...
                 ramdisk at 1 { ...
                 fdt at 1 { ...
                 fdt at 2 { ...
                 fdt at 3 { ...
         };

         configurations {
                 conf at 1 { ...
         };
};

one could in U-Boot do:

bootm 300000:kernel at 1
bootm 300000:kernel at 2 :ramdisk at 1 :fdt at 3
bootm 300000:kernel at 2 - 300000:fdt at 1
bootm 300000:config at 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