binman: Unwind the end-at-4gb special-case a little

Move the check for this further out, so that base_addr is computed in
Entry.WriteSymbols() rather than at lower levels.

Signed-off-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
Simon Glass 2024-08-26 13:11:41 -06:00
parent bce055338e
commit b73d0bb584
3 changed files with 18 additions and 18 deletions

View file

@ -404,12 +404,10 @@ class Image(section.Entry_section):
optional: True if the symbol is optional. If False this function
will raise if the symbol is not found
msg: Message to display if an error occurs
base_addr: Base address of image. This is added to the returned
image_pos in most cases so that the returned position indicates
where the targeted entry/binary has actually been loaded. But
if end-at-4gb is used, this is not done, since the binary is
already assumed to be linked to the ROM position and using
execute-in-place (XIP).
base_addr (int): Base address of image. This is added to the
returned value of image-pos so that the returned position
indicates where the targeted entry/binary has actually been
loaded
Returns:
Value that should be assigned to that symbol, or None if it was