diff options
author | Simon Glass <sjg@chromium.org> | 2020-10-27 02:40:10 +0300 |
---|---|---|
committer | Simon Glass <sjg@chromium.org> | 2020-10-29 23:42:59 +0300 |
commit | 4eec34c91f84d6c3915b300f0688f9b055e04dda (patch) | |
tree | 72599858724d4e4b7f7c79c7d26afc0225151403 /tools/binman/entry.py | |
parent | f90d906a275f85e7077d9a30ab82b20676b54645 (diff) | |
download | u-boot-4eec34c91f84d6c3915b300f0688f9b055e04dda.tar.xz |
binman: Expand docs and test for alignment
Alignment does form part of the entry once the image is written out, but
within binman the entry contents does not include the padding. Add
documentation to make this clear, as well as a test.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'tools/binman/entry.py')
-rw-r--r-- | tools/binman/entry.py | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/tools/binman/entry.py b/tools/binman/entry.py index e5d0aa52bd..0421129c03 100644 --- a/tools/binman/entry.py +++ b/tools/binman/entry.py @@ -48,9 +48,11 @@ class Entry(object): uncomp_size: Size of uncompressed data in bytes, if the entry is compressed, else None contents_size: Size of contents in bytes, 0 by default - align: Entry start offset alignment, or None + align: Entry start offset alignment relative to the start of the + containing section, or None align_size: Entry size alignment, or None - align_end: Entry end offset alignment, or None + align_end: Entry end offset alignment relative to the start of the + containing section, or None pad_before: Number of pad bytes before the contents when it is placed in the containing section, 0 if none. The pad bytes become part of the entry. |