Searched hist:"65 caa3d0ad72eb22c5e0a2a98aaa159e51eab43b" (Results 1 – 2 of 2) sorted by relevance
| /rk3399_ARM-atf/tools/fiptool/ |
| H A D | fiptool.h | 65caa3d0ad72eb22c5e0a2a98aaa159e51eab43b Thu Jan 26 18:56:58 UTC 2017 Masahiro Yamada <yamada.masahiro@socionext.com> 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>
|
| H A D | fiptool.c | 65caa3d0ad72eb22c5e0a2a98aaa159e51eab43b Thu Jan 26 18:56:58 UTC 2017 Masahiro Yamada <yamada.masahiro@socionext.com> 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>
|