summaryrefslogtreecommitdiff
path: root/board/m501sk
diff options
context:
space:
mode:
authorMarian Balakowicz <m8@semihalf.com>2008-02-21 17:20:20 +0100
committerMarian Balakowicz <m8@semihalf.com>2008-02-21 17:20:20 +0100
commitf50433d670ec2ee9e96abac67cdc6e5e061a810d (patch)
tree290a9d5e658517593dd659f6846be56d48e39319 /board/m501sk
parentfff888a1997ff7de9b29e24050fc4a0fd403ba16 (diff)
downloadu-boot-imx-f50433d670ec2ee9e96abac67cdc6e5e061a810d.zip
u-boot-imx-f50433d670ec2ee9e96abac67cdc6e5e061a810d.tar.gz
u-boot-imx-f50433d670ec2ee9e96abac67cdc6e5e061a810d.tar.bz2
[new uImage] Add fit_parse_conf() and fit_parse_subimage() routines
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>
Diffstat (limited to 'board/m501sk')
0 files changed, 0 insertions, 0 deletions