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


12 Aug, 2017

1 commit


08 Aug, 2017

1 commit


05 Aug, 2017

1 commit


01 Aug, 2017

1 commit

  • Migrate all remaining instances of CMD_NAND, CMD_NAND_TRIMFFS
    CMD_NAND_LOCK_UNLOCK and CMD_NAND_TORTURE from the headers into the
    defconfig files.

    Tested-by: Adam Ford
    Signed-off-by: Tom Rini
    Reviewed-by: Bin Meng

    Tom Rini
     

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
     

19 Jun, 2017

1 commit


10 Jun, 2017

1 commit

  • Almost all users of CONFIG_AM33XX/AM43XX have been migrated. Finish
    moving the last few over to Kconfig, and put all of the boards under the
    appropriate Kconfig chocie now. This board choice is non-optional, so
    remove that keyword on am33xx.

    Signed-off-by: Tom Rini

    Tom Rini
     

15 May, 2017

1 commit

  • Move this entry to Kconfig. As it is a hardware watchdog, select
    HW_WATCHDOG. While we could default to enabling this for all platforms,
    it is currently only enabled by default on AM33XX, so keep that logic
    today.

    Cc: Roger Meier
    Signed-off-by: Tom Rini

    Tom Rini
     

12 May, 2017

1 commit


28 Apr, 2017

1 commit


14 Mar, 2017

1 commit


28 Jan, 2017

1 commit


26 Jan, 2017

1 commit


24 Jan, 2017

1 commit


22 Jan, 2017

1 commit