Re: [PATCH 2/2] riscv: Provide __image_copy_{start_end} symbols in linkerscript

On Mon, Apr 07, 2025 at 01:10:32PM +0200, Jonas Karlman wrote: > Hi, > > On 2025-04-07 05:37, Yao Zi wrote: > > Binman looks for __image_copy_start to determine the base address of an > > entry if elf-base-sym isn't specified, which is missing in RISC-V port. > > This causes binman skips RISC-V SP

Re: [PATCH 2/2] riscv: Provide __image_copy_{start_end} symbols in linkerscript

+Heinrich Schuchardt On Mon, 7 Apr 2025 at 15:38, Yao Zi wrote: > > Binman looks for __image_copy_start to determine the base address of an > entry if elf-base-sym isn't specified, which is missing in RISC-V port. > This causes binman skips RISC-V SPL entries without filling addresses > into its

Re: [PATCH 2/2] riscv: Provide __image_copy_{start_end} symbols in linkerscript

Hi Yao, On Tue, 8 Apr 2025 at 03:32, Yao Zi wrote: > > On Mon, Apr 07, 2025 at 01:10:32PM +0200, Jonas Karlman wrote: > > Hi, > > > > On 2025-04-07 05:37, Yao Zi wrote: > > > Binman looks for __image_copy_start to determine the base address of an > > > entry if elf-base-sym isn't specified, which

Re: [PATCH 2/2] riscv: Provide __image_copy_{start_end} symbols in linkerscript

Hi, On 2025-04-07 05:37, Yao Zi wrote: > Binman looks for __image_copy_start to determine the base address of an > entry if elf-base-sym isn't specified, which is missing in RISC-V port. > This causes binman skips RISC-V SPL entries without filling addresses > into its .binman_sym_table section. >

[PATCH 2/2] riscv: Provide __image_copy_{start_end} symbols in linkerscript

Binman looks for __image_copy_start to determine the base address of an entry if elf-base-sym isn't specified, which is missing in RISC-V port. This causes binman skips RISC-V SPL entries without filling addresses into its .binman_sym_table section. This patch defines __image_copy_start in linkers