opensbi.git/firmware/fw_base.ldS, branch master

firmware: Rename __rel_dyn_start/end to __rela_dyn_start/end

2025-07-21T11:09:49Z

We are using and expecting the RELA format, not the REL format, and this is the conventional linker-generated name for the start/end symbols, so use it rather than confusing things by making it look like we're accessing .rel.dyn, which would be in the REL format with no explicit addend. Signed-off-by: Jessica Clarke Reviewed-by: Samuel Holland Tested-by: Samuel Holland Link: https://lore.kernel.org/r/20250710002937.44307-1-jrtc27@jrtc27.com Signed-off-by: Anup Patel

Makefile: enable --gc-sections

2024-11-06T10:59:39Z

The --gc-sections option enables the linker to perform garbage collection of unreferenced code and data, thereby reducing the binary size. The -ffunction-sections option will place each function into a separate section, so it is necessary to add .text.* to the linker script. Signed-off-by: Kele Zhang Signed-off-by: Yuan Tan Signed-off-by: Zhangjin Wu Reviewed-by: Bin Meng Reviewed-by: Xiang W Reviewed-by: Anup Patel

firmware: Bring back FW_TEXT_START as an optional parameter

2024-05-23T05:20:23Z

Bring back FW_TEXT_START as an optional parameter to allow users explicitly specify compile time address for loading debug symbols. When not specified, the FW_TEXT_START is assumed to be 0. Fixes: d4d2582eef7a ("firmware: remove FW_TEXT_START") Signed-off-by: Anup Patel Tested-by: Clément Léger

firmware: remove FW_TEXT_START

2024-04-10T04:20:24Z

Now opensbi can run at any address via dynamic relocation. We can remove FW_TEXT_START. Signed-off-by: Xiang W Reviewed-by: Anup Patel Tested-by: Anup Patel

firmware: always create dynsym section

2024-02-05T11:04:44Z

With a bare-metal linkers (e.g. riscv64-elf-ld), there exists no dynsym section. The dynsym section is not used by OpenSBI but discarding it makes linkers with dynamic library support unhappy. Signed-off-by: Leon M. Busch-George Reviewed-by: Anup Patel

firmware: Remove handling of R_RISCV_{32,64}

2023-10-06T03:51:23Z

Since everything is statically linked, we won't actually have R_RISCV_{32,64} relocations. No need to handle these. Fixes: 0f20e8adcf42 ("firmware: Support position independent execution") Signed-off-by: Vivian Wang Reviewed-by: Anup Patel

firmware: Remove ALIGN in .rela.dyn in linker script

2023-10-06T03:51:21Z

The .rela.dyn section should be exactly the size of the relocations, without padding. On RV64, .rela* sections are already aligned and there's no need for padding. On RV32, this adds padding up to 4 bytes, which, if present, confuses the relocation loop into processing an extra entry past the end of .rela*, and it crashes with an invalid memory access. Fixes: 0f20e8adcf42 ("firmware: Support position independent execution") Signed-off-by: Vivian Wang Reviewed-by: Anup Patel

firmware: Fix fw_rw_offset computation in fw_base.S

2023-01-27T03:09:49Z

It seems BFD just does totally nonsensical things for SHN_ABS symbols when producing position-independent outputs (both -pie and -shared) for various historical reasons, and so SHN_ABS symbols are still subject to relocation as far as BFD is concerned (except AArch64, which fixes it in limited cases that don’t apply here...). The above affects the _fw_rw_offset provided through fw_base.ldS linker script which results in OpenSBI firmware failing to boot when loaded at an address different from FW_TEXT_START. Fixes: c10e3fe5f9a1 ("firmware: Add RW section offset in scratch") Signed-off-by: Jessica Clarke Reported-by: Lad Prabhakar Tested-by: Lad Prabhakar Tested-by: Anup Patel Signed-off-by: Anup Patel

firmware: Move dynsym and reladyn sections to RX section

2023-01-23T04:36:14Z

Currently, the dynsym and reladyn sections are under RW data. They are moved to the Read-only/Executable region. Signed-off-by: Himanshu Chauhan Reviewed-by: Anup Patel

firmware: Split RO/RX and RW sections

2023-01-23T04:36:14Z

Split the RO/RX and RW sections so that they can have independent pmp entries with required permissions. The split size is ensured to be a power-of-2 as required by pmp. _fw_rw_offset symbol marks the beginning of the data section. Signed-off-by: Himanshu Chauhan Reviewed-by: Anup Patel