diff options
author | Palmer Dabbelt <palmer@rivosinc.com> | 2025-03-26 15:55:45 -0700 |
---|---|---|
committer | Palmer Dabbelt <palmer@rivosinc.com> | 2025-03-26 15:56:49 -0700 |
commit | f633de4aa4537c190a9842c3e84e77780621c615 (patch) | |
tree | 1ce477b4058436b9ce7a8834a44d3038d94ba8da /net/lapb/lapb_timer.c | |
parent | df02351331671abb26788bc13f6d276e26ae068f (diff) | |
parent | e1cf2d009b00fd890dbbcb8b79613ff538732559 (diff) | |
download | linux-f633de4aa4537c190a9842c3e84e77780621c615.tar.gz linux-f633de4aa4537c190a9842c3e84e77780621c615.tar.bz2 linux-f633de4aa4537c190a9842c3e84e77780621c615.zip |
Merge patch series "riscv: Relocatable NOMMU kernels"
Samuel Holland <samuel.holland@sifive.com> says:
Currently, RISC-V NOMMU kernels are linked at CONFIG_PAGE_OFFSET, and
since they are not relocatable, must be loaded at this address as well.
CONFIG_PAGE_OFFSET is not a user-visible Kconfig option, so its value is
not obvious, and users must patch the kernel source if they want to load
it at a different address.
Make NOMMU kernels more portable by making them relocatable by default.
This allows a single kernel binary to work when loaded at any address.
* b4-shazam-merge:
riscv: Remove CONFIG_PAGE_OFFSET
riscv: Support CONFIG_RELOCATABLE on riscv32
asm-generic: Always define Elf_Rel and Elf_Rela
riscv: Support CONFIG_RELOCATABLE on NOMMU
riscv: Allow NOMMU kernels to access all of RAM
riscv: Remove duplicate CONFIG_PAGE_OFFSET definition
Link: https://lore.kernel.org/r/20241026171441.3047904-1-samuel.holland@sifive.com
Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
Diffstat (limited to 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions