29 Feb, 2020

1 commit


07 Feb, 2020

1 commit


23 Jan, 2020

1 commit


05 Dec, 2019

4 commits


04 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
     

13 Nov, 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
     

09 Jul, 2019

1 commit

  • Enable the extended ENV options for AT91 and OMAP2PLUS in order to be
    able to use CONFIG_ENV_UBI_* on these architectures.

    As this change also makes the configs ENV_SIZE, ENV_SECT_SIZE,
    ENV_OFFSET visible to AT91 and OMAP2PLUS, migrate users of these to
    KConfig.

    This migration was run using an extended moveconfig.py which evaluates
    expressions such as "(512 << 10)". See patch ("moveconfig: expand
    simple expressions").

    All modified boards were built with SOURCE_DATE_EPOCH=0 before and
    after the change and successfully confirmed that the identical binary
    is generated (the only exception was igep00x0, which does not define
    CONFIG_ENV_IS_IN_UBI in the original board header. Once that is
    defined, the test passes too).

    hs: rebased patch to:
    68b90e57bc: "configs: tinker-rk3288 disable CONFIG_SPL_I2C_SUPPORT"

    Signed-off-by: Markus Klotzbuecher
    Cc: Heiko Schocher
    Cc: Eugen Hristev
    Cc: Tom Rini

    Markus Klotzbuecher
     

30 Apr, 2019

1 commit


01 Feb, 2019

1 commit


14 Nov, 2018

2 commits


04 Sep, 2018

1 commit


18 Aug, 2018

1 commit

  • Migrate boards which set bootlimit in the environment to Kconfig.

    We exclude gurnard_defconfig which includes a bootlimit=, but doesn't set
    CONFIG_BOOTCOUNT_LIMIT, so we'd fail to include a bootlimit setting
    if we migrated it.

    display5_defconfig and display5_factory_defconfig share a SYS_CONFIG_NAME,
    but only display5_defconfig enables CONFIG_BOOTCOUNT_LIMIT, so we fail to
    set bootlimit= in display5_factory_defconfig. This is okay because the
    display5_factory_defconfig doesn't need to have it set, as it is only
    meant to prepare the board in the factory.

    Environment changes for all modified configs as seen from buildman:

    boards.cfg is up to date. Nothing to do.
    Summary of 3 commits for 32 boards (8 threads, 1 job per thread)
    01: Merge git://git.denx.de/u-boot-x86
    arm: + draco etamin rastaban pxm2 display5 thuban rut
    02: Add BOOTCOUNT_BOOTLIMIT to set reboot limit
    03: Migrate bootlimit to Kconfig
    - display5_factory: bootlimit=3

    Signed-off-by: Alex Kiernan
    Reviewed-by: Lukasz Majewski

    Alex Kiernan
     

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
     

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


12 Apr, 2018

1 commit


09 Apr, 2018

1 commit


08 Apr, 2018

1 commit


07 Apr, 2018

1 commit


24 Feb, 2018

2 commits


15 Feb, 2018

1 commit


23 Jan, 2018

1 commit


06 Nov, 2017

1 commit


31 Oct, 2017

1 commit


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
     

04 Oct, 2017

2 commits


28 Aug, 2017

1 commit


15 Aug, 2017

1 commit


14 Aug, 2017

1 commit