23 Jan, 2020

1 commit


05 Dec, 2019

1 commit


21 Nov, 2019

1 commit

  • 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
     

08 Nov, 2019

1 commit


24 Oct, 2019

1 commit

  • The commit 4b0bcfa7c4ec ("Kconfig: Migrate CONFIG_BOOTM_* options")
    moved BOOTM_ options to Kconfig that's why align zynq defconfig with it.

    Disabling NETBSD was done by commit d6f48ea5ce18
    ("ARM: zynq: Do not enable NETBSD support by default").

    Signed-off-by: Michal Simek

    Michal Simek
     

08 Oct, 2019

1 commit


26 Aug, 2019

1 commit


02 Aug, 2019

1 commit

  • This converts the following to Kconfig:
    CONFIG_USE_PREBOOT
    CONFIG_PREBOOT

    Both are together in one commit, since otherwise the former causes kconfig
    to define the latter, which gives duplicate symbol errors.

    Includes a manual fixup for CONFIG_PREBOOT in ids8313_defconfig since the
    backslash lands in the wrong place. Similarly with socfpga_vining_fpga.

    Signed-off-by: Simon Glass

    Simon Glass
     

12 Jul, 2019

1 commit


15 Jun, 2019

1 commit


18 May, 2019

1 commit

  • While converting CONFIG_SYS_[DI]CACHE_OFF to Kconfig, there are instances
    where these configuration items are conditional on SPL. This commit adds SPL
    variants of these configuration items, uses CONFIG_IS_ENABLED(), and updates
    the configurations as required.

    Acked-by: Alexey Brodkin
    Signed-off-by: Trevor Woerner
    [trini: Make the default depend on the setting for full U-Boot, update
    more zynq hardware]
    Signed-off-by: Tom Rini

    Trevor Woerner
     

30 Apr, 2019

1 commit


26 Mar, 2019

1 commit

  • This converts the following to Kconfig:
    CONFIG_SF_DEFAULT_BUS
    CONFIG_SF_DEFAULT_CS
    CONFIG_SF_DEFAULT_MODE
    CONFIG_SF_DEFAULT_SPEED

    I use moveconfig script and then manual check on generated u-boot.cfg
    to solve the remaining issue.

    Signed-off-by: Patrick Delaunay

    Patrick Delaunay
     

14 Feb, 2019

1 commit

  • This patch is doing two things.
    1. Exchanging order of boot commands. distro_bootcmd is run first
    followed by Xilinx boot command.
    2. Remove CONFIG_BOOTCOMMAND from configs (and follow mainline) by
    creating Xilinx distribution bootcommand and wiring it as the last
    bootcommand.

    QSPI, NAND distribution boot command will be added later.

    Signed-off-by: Michal Simek

    Michal Simek
     

07 Feb, 2019

1 commit

  • Now that new SPI NOR layer uses stateless 4 byte opcodes by default,
    don't enable SPI_FLASH_BAR. For SPI controllers that cannot support
    4-byte addressing, (stm32_qspi.c, fsl_qspi.c, mtk_qspi.c, ich.c,
    renesas_rpc_spi.c) add an imply clause to enable SPI_FLASH_BAR so as to
    not break functionality.

    Signed-off-by: Vignesh R
    Tested-by: Simon Goldschmidt
    Tested-by: Stefan Roese
    Tested-by: Horatiu Vultur
    Reviewed-by: Jagan Teki
    Tested-by: Jagan Teki #zynq-microzed

    Vignesh R
     

01 Feb, 2019

1 commit


04 Sep, 2018

1 commit


18 Aug, 2018

1 commit


06 Aug, 2018

1 commit


11 May, 2018

1 commit

  • Now that showing silicon version is part of the CPU
    info display, let's remove checkboard().

    Note that the generic show_board_info() will still
    show the DT 'model' property. For instance:

    U-Boot 2018.05-rc2-00025-g611b3ee0159b (Apr 19 2018 - 11:23:12 +0200)

    CPU: Zynq 7z045
    Silicon: v1.0
    Model: Zynq ZC706 Development Board
    I2C: ready

    Based on patches from Ariel D'Alessandro ,
    and Ezequiel Garcia

    mini configuration doesn't need to show this information.

    Signed-off-by: Michal Simek

    Michal Simek
     

28 Apr, 2018

1 commit


17 Apr, 2018

1 commit

  • We enabled CONFIG_ISO_PARTITION by default for distro boot, so that U-Boot
    could load distro images that usually get shipped as iso images. These images
    usually come with a board agnostic boot environment.

    However, there is very little point in having ISO support enabled (for anyone
    really) in SPL, as the whole idea of SPL is to load U-Boot proper which again
    is board specific. So the fact that we enable ISO support in U-Boot proper does
    not mean at all that we want ISO support in U-Boot SPL.

    Hence, let's remove the Kconfig dependency. Along the way, let's also clean up
    all those default configs that disabled SPL ISO support.

    Signed-off-by: Alexander Graf

    Alexander Graf
     

12 Apr, 2018

1 commit


23 Mar, 2018

1 commit


01 Mar, 2018

1 commit


23 Feb, 2018

1 commit


30 Jan, 2018

6 commits


15 Dec, 2017

1 commit


28 Nov, 2017

4 commits


11 Oct, 2017

1 commit

  • Having this as a 'default y' is rather annoying because it doesn't
    actually compile unless other options are defined in the board header:

    ../cmd/bootm.c: In function 'do_imls_nor':
    ../cmd/bootm.c:330:7: error: 'CONFIG_SYS_MAX_FLASH_BANKS' undeclared (first use in this function); did you mean 'CONFIG_SYS_MAX_FLASH_SECT'?
    i < CONFIG_SYS_MAX_FLASH_BANKS; ++i, ++info) {

    Make it 'default n' so people who develop new boards that start from a
    blank defconfig have one less compilation failure to debug.

    Signed-off-by: Tuomas Tynkkynen

    Tuomas Tynkkynen
     

28 Aug, 2017

1 commit


26 Jul, 2017

1 commit

  • This converts the following to Kconfig:
    CONFIG_ENV_IS_IN_MMC
    CONFIG_ENV_IS_IN_NAND
    CONFIG_ENV_IS_IN_UBI
    CONFIG_ENV_IS_NOWHERE

    In fact this already exists for sunxi as a 'choice' config. However not
    all the choices are available in Kconfig yet so we cannot use that. It
    would lead to more than one option being set.

    In addition, one purpose of this series is to allow the environment to be
    stored in more than one place. So the existing choice is converted to a
    normal config allowing each option to be set independently.

    There are not many opportunities for Kconfig updates to reduce the size of
    this patch. This was tested with

    ./tools/moveconfig.py -i CONFIG_ENV_IS_IN_MMC

    And then manual updates. This is because for CHAIN_OF_TRUST boards they
    can only have ENV_IS_NOWHERE set, so we enforce that via Kconfig logic
    now.

    Signed-off-by: Simon Glass
    Signed-off-by: Tom Rini

    Simon Glass