[U-Boot] pedantry: is a FIT image really an enhanced type of uImage?

[Robert P. J. Day]

  a matter of picky terminology, but i'm reading the docs on FIT
images, and in doc/uImage.FIT/source_file_format.txt, early on, i
read:

  "U-Boot new uImage source file format (bindings definition)
  ...
  This document defines new uImage structure ..."

and so on and so on ... a number of references that appear to describe
FIT images as newer and enhanced types of uImage.

  but i understood that the proper definition of uImage is the
"legacy" form for u-boot, and there are now alternates such as zImage
and, yes, FIT images.

  the man page for "mkimage" reads:

  SYNOPSIS
       mkimage -l [uimage file name]

       mkimage [options] -f [image tree source file] [uimage file name]

       mkimage [options] -F [uimage file name]

       mkimage [options] (legacy mode)

and further down reads:

  OPTIONS
       List image information:

       -l [uimage file name]
              mkimage lists the information contained in the header of an existing U-Boot image.

       Create old legacy image:

       ... snip ...

       Create FIT image:

       ... snip ...

and that latter part seems to suggest that FIT images are *distinct*
from the legacy images.

  so what is the technically proper way to describe a FIT image? just
another type of uImage? or a wholly new type of image?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================