23 Jan, 2020

1 commit


05 Dec, 2019

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
     

23 Sep, 2019

1 commit


02 Aug, 2019

1 commit


21 Jun, 2019

1 commit


27 May, 2019

1 commit


30 Apr, 2019

2 commits


13 Feb, 2019

1 commit

  • It should not be necessary to adjust CMD_BOOTEFI_HELLO_COMPILE in config
    files.

    arch/arm/lib/crt0_arm_efi.S cannot be compiled in thumbs mode. We can
    disable CMD_BOOTEFI_HELLO_COMPILE for CONFIG_CPU_V7M. So there is no longer
    a need to disable it in stm32 configs.

    helloworld.efi can be built without problems on x86_64. So there is no need
    to disable it in chromebook_link64_defconfig and qemu-x86_64_defconfig.

    Same is true for ARM V7A. So do not disable CMD_BOOTEFI_HELLO_COMPILE in
    kp_imx6q_tpc_defconfig.

    Some architecture checks are already make for EFI_LOADER. There is no need
    to repeat them for CMD_BOOTEFI_HELLO_COMPILE

    Signed-off-by: Heinrich Schuchardt
    Reviewed-by: Simon Glass
    Reviewed-by: Patrice.Chotard@st.com
    Signed-off-by: Alexander Graf

    Heinrich Schuchardt
     

13 Dec, 2018

1 commit

  • Building U-Boot with CONFIG_PCI and CONFIG_DM_PCI enabled, but
    CONFIG_SPL_PCI_SUPPORT disabled, results in following linker
    error:

    lib/built-in.o: In function `fdtdec_get_pci_bar32':
    lib/fdtdec.c:305: undefined reference to `dm_pci_read_bar32'
    fdtdec.c:305:(.text.fdtdec_get_pci_bar32+0x24): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `dm_pci_read_bar32'

    This is because reference to dm_pci_read_bar32() remains in lib/fdtdec.c
    while SPL build does not descend into drivers/pci directory in
    drivers/Makefile if CONFIG_SPL_PCI_SUPPORT is not enabled.

    Fix this by applying appropriate #define guards in lib/fdtdec.c.
    It looks like ns16550.c has the same problem, so fixed that too.

    To simplify this, CONFIG_SPL_PCI_SUPPORT is renamed to CONFIG_SPL_PCI
    (enables use of CONFIG_IS_ENABLED() macro).

    Suggested-by: Vignesh R
    Signed-off-by: Sekhar Nori
    Reviewed-by: Lokesh Vutla
    Reviewed-by: Tom Rini

    Sekhar Nori
     

14 Nov, 2018

1 commit


09 Oct, 2018

1 commit


04 Sep, 2018

1 commit


18 Aug, 2018

1 commit


17 Aug, 2018

1 commit

  • We have the following cases:
    - CONFIG_NR_DRAM_BANKS was defined, migrate normally
    - CONFIG_NR_DRAM_BANKS_MAX was defined and then used for
    CONFIG_NR_DRAM_BANKS after a check, just migrate it over now.
    - CONFIG_NR_DRAM_BANKS was very oddly defined on p2771-0000-* (to 1024 +
    2), set this to 8.

    Signed-off-by: Tom Rini

    Tom Rini
     

20 Jul, 2018

1 commit


04 Jun, 2018

1 commit


28 Apr, 2018

1 commit

  • This converts the following to Kconfig:
    CONFIG_SPI

    This partly involves updating code that assumes that CONFIG_SPI implies
    things that are specific to the MPC8xx SPI driver. For now, just update
    the CONFIG tests. This also involves reworking the default for
    CONFIG_SYS_DEF_EEPROM_ADDR so that we don't set it when we cannot make a
    reasonable default, as it does not cause any compile failures.

    Signed-off-by: Adam Ford
    Signed-off-by: Tom Rini

    Adam Ford
     

17 Apr, 2018

1 commit


09 Apr, 2018

2 commits


24 Feb, 2018

1 commit

  • This converts the following to Kconfig:
    CONFIG_BOOTP_BOOTPATH
    CONFIG_BOOTP_DNS
    CONFIG_BOOTP_GATEWAY
    CONFIG_BOOTP_HOSTNAME
    CONFIG_BOOTP_PXE
    CONFIG_BOOTP_SUBNETMASK
    CONFIG_CMDLINE_EDITING
    CONFIG_AUTO_COMPLETE
    CONFIG_SYS_LONGHELP
    CONFIG_SUPPORT_RAW_INITRD
    CONFIG_ENV_VARS_UBOOT_CONFIG

    Signed-off-by: Adam Ford
    [trini: Re-run the migration]
    Signed-off-by: Tom Rini

    Adam Ford
     

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
     

16 Sep, 2017

1 commit


24 Aug, 2017

1 commit


15 Aug, 2017

2 commits


13 Aug, 2017

1 commit

  • To fully support DM timer in SPL and TPL, we need a few things cleaned
    up and normalised:
    - inclusion of the uclass and drivers should be an all-or-nothing
    decision for each stage and under control of $(SPL_TPL_)TIMER
    instead of having the two-level configuration with TIMER and
    $(SPL_TPL_)TIMER_SUPPORT
    - when $(SPL_TPL_)TIMER is enabled, the ARMv8 generic timer code can
    not be compiled in

    This normalises configuration to $(SPL_TPL_)TIMER and moves the config
    options to drivers/timer/Kconfig (and cleans up the collateral damage
    to some defconfigs that had SPL_TIMER_SUPPORT enabled).

    Signed-off-by: Philipp Tomsich
    Reviewed-by: Simon Glass

    Philipp Tomsich
     

12 Aug, 2017

1 commit


01 Aug, 2017

9 commits

  • After MMC is converted to DM, convert to use DM SCSI as well for all
    x86 boards and imply BLK for both MMC and SCSI drivers.

    CONFIG_SCSI_DEV_LIST is no longer used. Clean them up.

    Signed-off-by: Bin Meng
    Reviewed-by: Simon Glass

    Bin Meng
     
  • Only a specific type of SPI flash exists on a board, having board
    Kconfig to select the SPI flash seems to make more sense. Other
    flash types are not necessary except coreboot, which implies all
    available flash drivers there.

    Signed-off-by: Bin Meng
    Reviewed-by: Simon Glass

    Bin Meng
     
  • Imply drivers that are working with Ivybridge platform in the
    platform Kconfig.

    Signed-off-by: Bin Meng
    Reviewed-by: Simon Glass

    Bin Meng
     
  • Now that all x86 boards have been converted to use DM, we can imply
    these uclass drivers (DM_ETH, DM_RTC, DM_USB, DM_VIDEO) from the
    top level.

    Previously DM_GPIO, DM_KEYBOARD, DM_SERIAL, DM_SPI, DM_SPI_FLASH
    are selected. Change to use 'imply' to allow them to be removed.

    Note with this change, chromebook_link64 build fails:

    common/built-in.o:(.data.env_htab+0xc): undefined reference to 'env_flags_validate'
    lib/built-in.o: In function `hsearch_r':
    lib/hashtable.c:380: undefined reference to 'env_callback_init'
    lib/hashtable.c:382: undefined reference to 'env_flags_init'
    make[1]: *** [spl/u-boot-spl] Error 1

    CONFIG_SPL_ENV_SUPPORT is required for chromebook_link64 to build
    again. This is just a workaround as it is not needed at all. See
    commit bda40d5 "x86: qemu: Add a config for 64-bit U-Boot" for
    the same issue seen on QEMU 64-bit target.

    Signed-off-by: Bin Meng
    Reviewed-by: Andy Shevchenko
    Reviewed-by: Simon Glass

    Bin Meng
     
  • This is a must have for all x86 boards.

    Signed-off-by: Bin Meng
    Reviewed-by: Andy Shevchenko
    Reviewed-by: Simon Glass

    Bin Meng
     
  • Platform knows whether MRC cache is implemented, but using it can
    be a choice of a specific board.

    Signed-off-by: Bin Meng
    Reviewed-by: Simon Glass

    Bin Meng
     
  • PCI is the de facto interconnect bus in an x86 system.

    Signed-off-by: Bin Meng
    Reviewed-by: Andy Shevchenko
    Reviewed-by: Simon Glass

    Bin Meng
     
  • x86 is using the built-in libgcc implementation and this cannot be
    turned off.

    Signed-off-by: Bin Meng
    Reviewed-by: Andy Shevchenko
    Reviewed-by: Simon Glass

    Bin Meng
     
  • Without a timer, U-Boot just doesn't boot. This is not something
    we can turn off.

    Signed-off-by: Bin Meng
    Reviewed-by: Andy Shevchenko
    Reviewed-by: Simon Glass

    Bin Meng