Hi Yao, On 2026-07-01T11:17:53, Yao Zi <[email protected]> wrote: > image: Take entry point as an output of setup_booti
The function is called booti_setup(), not setup_booti - please fix the subject. > > For LoongArch the start of the image is not the entry > point to the image. > > We refactor the code base to allow entry point to be > supplied by setup_booti. Use imperative mode: Refactor the code base to allow... > > Signed-off-by: Jiaxun Yang <[email protected]> > Signed-off-by: Yao Zi <[email protected]> > > arch/arm/lib/image.c | 3 ++- > arch/riscv/lib/image.c | 4 +++- > arch/sandbox/lib/bootm.c | 2 +- > boot/bootm.c | 5 +++-- > cmd/booti.c | 5 +++-- > common/spl/spl.c | 9 +++++---- > include/image.h | 3 ++- > 7 files changed, 19 insertions(+), 12 deletions(-) > diff --git a/include/image.h b/include/image.h > @@ -1131,11 +1131,12 @@ int bootz_setup(ulong image, ulong *start, ulong > *end); > * @image: Address of image > * @start: Returns start address of image > * @size : Returns size image > + * @entry: Returns entry point of image > * @force_reloc: Ignore image->ep field, always place image to RAM start > * Return: 0 if OK, 1 if the image was not recognised > */ > int booti_setup(ulong image, ulong *relocated_addr, ulong *size, > - bool force_reloc); > + ulong *entry, bool force_reloc); While you are here, please fix the @start: tag to match the actual parameter name (relocated_addr), and drop 'aarch64' from the description above since this now covers arm64, RISC-V and LoongArch. Regards, Simon
