microblaze: drop CONFIG_NEEDS_MANUAL_RELOC

Microblaze and m68k are the only remaining architectures that still enable
CONFIG_NEEDS_MANUAL_RELOC by default.

Microblaze has had runtime relocation support using CONFIG_STATIC_RELA for
quite some time, since commit d58c007498 ("microblaze: Add support for run
time relocation"). Drop support for CONFIG_NEEDS_MANUAL_RELOC and make
runtime relocation the default, as the rest of the architectures do.

Reviewed-by: Michal Simek <[email protected]>
Signed-off-by: Ovidiu Panait <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Michal Simek <[email protected]>

diff --git a/arch/microblaze/Kconfig b/arch/microblaze/Kconfig
index ce157a79ccc17c88dcff163b7ddb70ad7d8ae8db..e38c9f6d71174241bd1dc8628e560006767cbd36 100644 (file)
--- a/arch/microblaze/Kconfig
+++ b/arch/microblaze/Kconfig
@@ -4,19 +4,8 @@ menu "MicroBlaze architecture"
 config SYS_ARCH
        default "microblaze"
 
-config NEEDS_MANUAL_RELOC
-       bool "Disable position-independent pre-relocation code"
-       default y
-       help
-         U-Boot expects to be linked to a specific hard-coded address, and to
-         be loaded to and run from that address. This option lifts that
-         restriction, thus allowing the code to be loaded to and executed from
-         almost any 4K aligned address. This logic relies on the relocation
-         information that is embedded in the binary to support U-Boot
-         relocating itself to the top-of-RAM later during execution.
-
 config STATIC_RELA
-       def_bool y if !NEEDS_MANUAL_RELOC
+       def_bool y
 
 choice
        prompt "Target select"