20 Feb, 2020

1 commit


19 Feb, 2020

1 commit


30 Jan, 2020

1 commit


23 Jan, 2020

1 commit


21 Nov, 2019

2 commits

  • - In ARMv8 NXP Layerscape platforms we also need to make use of
    CONFIG_SYS_RELOC_GD_ENV_ADDR now, do so.
    - On ENV_IS_IN_REMOTE, CONFIG_ENV_OFFSET is never used, drop the define
    to 0.
    - Add Kconfig entry for ENV_ADDR.
    - Make ENV_ADDR / ENV_OFFSET depend on the env locations that use it.
    - Add ENV_xxx_REDUND options that depend on their primary option and
    SYS_REDUNDAND_ENVIRONMENT
    - On a number of PowerPC platforms, use SPL_ENV_ADDR not CONFIG_ENV_ADDR
    for the pre-main-U-Boot environment location.
    - On ENV_IS_IN_SPI_FLASH, check not for CONFIG_ENV_ADDR being set but
    rather it being non-zero, as it will now be zero by default.
    - Rework the env_offset absolute in env/embedded.o to not use
    CONFIG_ENV_OFFSET as it was the only use of ENV_OFFSET within
    ENV_IS_IN_FLASH.
    - Migrate all platforms.

    Cc: Wolfgang Denk
    Cc: Joe Hershberger
    Cc: Patrick Delaunay
    Cc: uboot-stm32@st-md-mailman.stormreply.com
    Signed-off-by: Tom Rini
    Acked-by: Joe Hershberger
    Reviewed-by: Simon Goldschmidt

    Tom Rini
     
  • Today in initr_reloc_global_data() we use some non-obvious tests to
    determine if we need to relocate the env_addr within gd or not. In
    order to facilitate migration of other symbols to Kconfig we need to
    introduce a new symbol for this particular use case.

    Cc: Wolfgang Denk
    Cc: Joe Hershberger
    Signed-off-by: Tom Rini

    Tom Rini
     

12 Nov, 2019

1 commit


10 Nov, 2019

2 commits

  • Use the same SPL_STACK_R_ADDR in Kconfig instead of each board config;
    default to 0x4000000(64MB) instead of 0x80000(512KB) for this address
    can support all the SoCs including those may have only 64MB memory, and
    also reserve enough space for atf, kernel(in falcon mode) loading.

    After the ATF entry move to 0x40000, the stack from 0x80000 may be override
    when loading ATF bl31.

    Signed-off-by: Kever Yang

    Kever Yang
     
  • We use to reserve IRAM to avoid the SPL text overlap with ATF M0 code,
    and when we introduce the TPL, the SPL space is in DRAM, we reserve
    space to avoid SPL text overlap with ATF bl31.

    Now we decide to move ATF entry point to 0x40000 instead of 0x1000,
    so that the SPL can have 0x4000 as code size and no need to reserve
    space or relocate before loading ATF.

    The mainline ATF has update since:
    0aad563c rockchip: Update BL31_BASE to 0x40000

    Signed-off-by: Kever Yang

    Kever Yang
     

08 Nov, 2019

1 commit


23 Aug, 2019

1 commit


05 Aug, 2019

1 commit

  • Add devicetree support for Khadas Edge-Captain.
    Khadas Captain is the carrier board for Khadas Edge.

    Specification
    - Rockchip RK3399
    - Dual-Channel 2GB/4GB LPDDR4
    - SD card slot
    - Onboard 16GB/32GB/128GB eMMC
    - RTL8211FD 1Gbps
    - AP6356S/AP6398S WiFI/BT
    - HDMI Out, DP, MIPI DSI/CSI, eDP
    - USB 3.0, 2.0
    - USB Type C power and data
    - GPIO expansion ports
    - Full 4 Lane M.2 Socket
    - 16MB SPI Flash
    - IR
    - Programmable MCU

    Commit details of rk3399-khadas-edge-*.dts sync from Linux 5.3-rc2:
    "arm64: dts: rockchip: Add support for Khadas Edge/Edge-V/Captain boards"
    (sha1: c2aacceedc86af87428d998e23a1aca24fd8aa2e)

    Signed-off-by: Nick Xie
    Tested-by: Chris Webb
    Reviewed-by: Kever Yang

    Nick Xie