All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Sieka <tur@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 3/5] [new uImage] Add fit_parse_conf() and	fit_parse_subimage() routines
Date: Fri, 22 Feb 2008 10:48:09 +0100	[thread overview]
Message-ID: <47BE9A59.2090100@semihalf.com> (raw)
In-Reply-To: <F9E24F68-5094-4E7A-9165-27445608F70D@kernel.crashing.org>

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

  reply	other threads:[~2008-02-22  9:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 17:55 [U-Boot-Users] [PATCH 0/5 RESEND] [new uImage] patchset4 - assorted patches Bartlomiej Sieka
2008-02-21 17:55 ` [U-Boot-Users] [PATCH 1/5] [new uImage] Pull in libfdt if CONFIG_FIT is enabled Bartlomiej Sieka
2008-02-21 17:55 ` [U-Boot-Users] [PATCH 2/5] [new uImage] Add gen_get_image() routine Bartlomiej Sieka
2008-02-21 17:55 ` [U-Boot-Users] [PATCH 3/5] [new uImage] Add fit_parse_conf() and fit_parse_subimage() routines Bartlomiej Sieka
2008-02-21 18:32   ` Kumar Gala
2008-02-22  9:48     ` Bartlomiej Sieka [this message]
2008-02-21 17:55 ` [U-Boot-Users] [PATCH 4/5] [new uImage] Rename and move print_image_hdr() routine Bartlomiej Sieka
2008-02-21 17:56 ` [U-Boot-Users] [PATCH 5/5] [new uImage] Fix erroneous use of image_get_magic() in fdc/usb cmds Bartlomiej Sieka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47BE9A59.2090100@semihalf.com \
    --to=tur@semihalf.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.