Re: [PATCH v4 7/7] binman: fit: document how ELF load addresses are determined

Simon Glass <[email protected]>
Newsgroups org.u-boot-project.lists.u-boot
Message-ID <CAFLszTijV2z9zKxv08s6g+sWV9HdbasT91UV1bPTRdKK6wu0cA@mail.gmail.com>
On 2026-07-31T00:13:34, Aristo Chen <[email protected]> wrote:
> binman: fit: document how ELF load addresses are determined
>
> The fit,load property confuses users because the load address is
> taken from the ELF file rather than being specified in the binman
> node. Document how to inspect an ELF file to find out where its
> segments will be loaded, using readelf, the linker script or objdump,
> and point at the elf_sections and elf_sections_tee test linker
> scripts as examples of two components placed to avoid overlapping
> memory. Also note that the mkimage load address overlap check works
> on packaged data sizes and therefore assumes uncompressed images.
>
> Compared to the previously applied version of this change, the text
> now lives in the fit etype docstring. The entry documentation is
> produced from docstrings by the binman_docs Sphinx extension at
> documentation build time, so no pre-generated file needs updating.
>
> Signed-off-by: Aristo Chen <[email protected]>
>
> tools/binman/etype/fit.py | 26 ++++++++++++++++++++++++++
>  1 file changed, 26 insertions(+)

Reviewed-by: Simon Glass <[email protected]>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.