opensbi.git/firmware/fw_payload.S, branch v0.7

firmware: Fix placement of .align directives

2020-01-10T04:00:27Z

Move the .align directives after switching the section. We want to align the start of the current section, not the end of the previous section. This also obsoletes the misguided workaround of disabling relaxation. Signed-off-by: Andreas Schwab Reviewed-by: Anup Patel

firmware: Improve comments for fw_prev_arg1() and fw_next_arg1()

2019-12-27T03:24:24Z

The state of a0, a1, and a2 registers in fw_prev_arg1() and fw_next_arg1() is same as passed by previous booting stage so we add this info in comments for both these functions. Signed-off-by: Anup Patel

firmware: Return real DTB address when FW_xyz_FDT_ADDR is not defined

2019-12-27T03:18:17Z

Function fw_next_arg1 in firmware/fw_jump.S:59 and firmware/fw_payload.S:63 should return real dtb address(if specified in a1) in a0, in case we don't want to specify FW_xyz_FDT_ADDR when compiling. Signed-off-by: Liu Yibin Reviewed-by: Anup Patel

firmware: Add preferred boot HART field in struct fw_dynamic_info

2019-11-15T12:11:18Z

It has been reported that link address range of previous booting stage (such as U-Boot SPL) can overlap the link address rage of FW_DYNAMIC. This means self-relocation in FW_DYNAMIC can potentially corrupt previous booting stage if any of the secondary HART enter FW_DYNAMIC before primary HART. To tackle this, we add preferred boot HART field (i.e boot_hart) in struct fw_dyanmic_info. We use this field to force secondary HARTs into relocation wait loop till preferred/primary boot HART enters FW_DYNAMIC completes self-relocation. If preferred boot HART is not available then we fall back to relocation lottery approach. Signed-off-by: Anup Patel Reviewed-by: Atish Patra

firmware: Fix compile error for FW_PAYLOAD with latest GCC binutils

2019-10-28T14:41:42Z

We get following compile error for FW_PAYLOAD with latest GCC binutils: fw_payload.o(.text+0x1961): 15 bytes required for alignment to 16-byte boundary, but only 14 present Further investigating, it turn-out to be a known issue with RISC-V GCC binutils. (Refer, https://github.com/riscv/riscv-gnu-toolchain/issues/298) As a work-around, we disable relaxation when including DTB and PAYLOAD binary in fw_payload.S. Reported-by: David Abdurachmanov Signed-off-by: Anup Patel Tested-by: David Abdurachmanov Reviewed-by: Atish Patra

firmware: Allow firmwares to provide next mode and options

2019-05-10T06:56:22Z

This patch extends existing firmwares (i.e. fw_jump and fw_payload) to explicitly provide next mode and options to fw_base. We also introduce fw_save_info() which is called by fw_base very early on boot HART. This function can be used by existing firmwares (i.e. fw_jump and fw_payload) to save information passed by previous booting stage. Overall, this is a preparatory patch for implementing fw_dynamic. Signed-off-by: Anup Patel Reviewed-by: Alistair Francis Reviewed-by: Atish Patra

firmware: Ensure the payloads are 4 bit alligned

2019-02-15T04:26:47Z

We expect the payloads to be 4 bit alligned as we later AND them with ~0xf. As most of the addresses are manually specified we don't really need this, but better to be over cautious. Signed-off-by: Alistair Francis

firwmare: don't expand macros in FW_PAYLOAD_PATH

2019-02-06T05:09:17Z

Signed-off-by: Andreas Schwab

all: Update copyright header in all files

2019-01-24T08:37:47Z

This patch updates copyright header in all files as follows: 1. Makes "SPDX-License-Identifier: BSD-2-Clause" as first line 2. Change copyright year to 2019 for Western Digital Signed-off-by: Anup Patel

firmware: Rename fw_common.S to fw_base.S

2018-12-27T04:00:12Z

The fw_common.S is the base firmware extendend by fw_jump and fw_payload. This patch renames fw_common.S to fw_base.S to have more clear/intutive name for base firmware. Signed-off-by: Anup Patel