On Tue, Mar 29, 2022 at 02:02:38PM -0400, Sean Anderson wrote:
If .bss does not immediately follow the end of the image, then CONFIG_SPL_SEPARATE_BSS must be selected. Typically, the location of bss is specified by using CONFIG_SPL_BSS_START_ADDR in a linker script. On these arches, CONFIG_SPL_SEPARATE_BSS should be enabled. If there is an option to use an alternate boot script (e.g. CONFIG_SPL_LDSCRIPT is just a default), just imply. If there is not, select.
Signed-off-by: Sean Anderson sean.anderson@seco.com
This gives "WARNING: unmet direct dependencies detected for SPL_SEPARATE_BSS" for: boston32r2 boston32r2el boston32r6 boston32r6el malta maltael imgtec_xilfpga ap121 ap143 ap152 tplink_wdr4300 netgear_cg3100d_ram comtrend_ar5315u_ram comtrend_vr3032u_ram comtrend_ar5387un_ram sagem_f@st1704_ram comtrend_ct5361_ram huawei_hg556a_ram sfr_nb4-ser_ram netgear_dgnd3700v2_ram comtrend_wap5813n_ram bcm968380gerg_ram mscc_jr2 mscc_luton mscc_ocelot mscc_serval mscc_servalt pic32mzdask boston64r2 boston64r2el boston64r6 boston64r6el malta64 malta64el octeon_ebb7304 octeon_nic23 ae350_rv32 ae350_rv32_xip ae350_rv64 ae350_rv64_xip qemu-riscv32 qemu-riscv32_smode qemu-riscv64 qemu-riscv64_smode microchip_mpfs_icicle openpiton_riscv64 sipeed_maix_bitm sipeed_maix_smode