summaryrefslogtreecommitdiff
path: root/doc/uImage.FIT
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2022-09-06 20:26:52 -0600
committerTom Rini <trini@konsulko.com>2022-09-29 16:07:57 -0400
commitf3543e69442ca393e52df253d9c5d45bc189d471 (patch)
tree99423df56b15a01188099161332c6c8aed301972 /doc/uImage.FIT
parentda79b2f25e5352a8e09b96ecef56df009f03c0b5 (diff)
treewide: Drop image_header_t typedef
This is not needed and we should avoid typedefs. Use the struct instead and rename it to indicate that it really is a legacy struct. Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc/uImage.FIT')
-rw-r--r--doc/uImage.FIT/source_file_format.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/uImage.FIT/source_file_format.txt b/doc/uImage.FIT/source_file_format.txt
index 6870111840..0a03c942bd 100644
--- a/doc/uImage.FIT/source_file_format.txt
+++ b/doc/uImage.FIT/source_file_format.txt
@@ -23,7 +23,7 @@ in the system memory and passed to bootm as a arguments. Some of them may be
missing: FDT is not present for legacy platforms, ramdisk is always optional.
Additionally, old uImage format has been extended to support multi sub-images
but the support is limited by simple format of the legacy uImage structure.
-Single binary header 'struct image_header' is not flexible enough to cover all
+Single binary header 'struct legacy_img_hdr' is not flexible enough to cover all
possible scenarios.
All those factors combined clearly show that there is a need for new, more