[U-Boot-Users] [PATCH] Add 'imload' command

[Wolfgang Denk <wd@denx.de>]

In message <Pine.LNX.4.64.0802122307330.22593@blarg.am.freescale.net> you wrote:
> 'imload' provides a more direct means to load from an image file.

What exactly is an "image file" here (which sorts of images are
allowed?) and what does "load" mean (which actions are performed on
the file)?

> Also created a load_image routine out of the code in do_bootm() that
> is shared between do_bootm() and do_imload().

Hm... bootm is restrictred to a certain sub-set of image types. imload
on the other hand sounds pretty generic to me and should not have such
restrictions.

> +	switch (image_get_comp (hdr)) {
> +	case IH_COMP_NONE:
> +		if (dst == (ulong)hdr) {
> +			printf ("   XIP %s ... ", type_name);

This is an ugly hack in the old code that should be removed by the new
implementation.

> +	"imload  - load image from application image\n",
> +	"[addr] [load addr]\n"

What exactly is an "application image" ?

> +	"    - load image from application image located at address 'addr'\n"
> +	"      or $loadaddr if 'addr' is not provided to either the load\n"
> +	"      address specified in the application image header or the\n"
> +	"      'load addr' argument; this includes verification of the\n"
> +	"      image contents (magic number, header and payload checksums)\n"

Please be terse. We don't want to spend the memory footprint on prosa.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Data is a lot like humans: It is  born.  Matures.  Gets  married  to
other  data, divorced. Gets old. One thing that it doesn't do is die.
It has to be killed."                                 - Arthur Miller