diff options
| author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2017-01-27 03:56:58 +0900 |
|---|---|---|
| committer | Masahiro Yamada <yamada.masahiro@socionext.com> | 2017-01-28 14:44:21 +0900 |
| commit | 65caa3d0ad72eb22c5e0a2a98aaa159e51eab43b (patch) | |
| tree | c683ef6e236acbdfb0a0596103cf806b1e4f3e4e /make_helpers | |
| parent | a1da83f5fc91b15761fa418aedf14e155a7e24c6 (diff) | |
| download | platform_external_arm-trusted-firmware-65caa3d0ad72eb22c5e0a2a98aaa159e51eab43b.tar.gz platform_external_arm-trusted-firmware-65caa3d0ad72eb22c5e0a2a98aaa159e51eab43b.tar.bz2 platform_external_arm-trusted-firmware-65caa3d0ad72eb22c5e0a2a98aaa159e51eab43b.zip | |
fiptool: embed fip_toc_entry in struct image
The struct image has "uuid" and "size" to memorize the field values
they had in the TOC entry. So, parse_fip() copies them from struct
fip_toc_entry to struct image, then pack_images() copies them back
to struct fip_toc_entry.
The next commit (support --align option) will require to save the
"offset" field as well. This makes me realize that struct image
can embed struct fip_toc_entry.
This commit will allow the "flags" field to persevere the "update"
command. At this moment, the "flags" is not used in a useful way.
(Yet, platforms can save their own parameters in the flags field.)
It makes sense to save it unless users explicitly replace the image.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'make_helpers')
0 files changed, 0 insertions, 0 deletions