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 Feb, 2018

1 commit

  • On the NIOS2 and Xtensa architectures, we do not have
    CONFIG_SYS_TEXT_BASE set. This is a strict migration of the current
    values into the defconfig and removing them from the headers.

    I did not attempt to add more default values in and for now will leave
    that to maintainers.

    Signed-off-by: Tom Rini

    Tom Rini
     

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
     

23 May, 2017

2 commits


22 May, 2017

3 commits

  • This converts the following to Kconfig:
    CONFIG_CMD_ERRATA

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

    Simon Glass
     
  • This converts the following to Kconfig:
    CONFIG_CMD_EEPROM
    CONFIG_CMD_EEPROM_LAYOUT
    CONFIG_EEPROM_LAYOUT_HELP_STRING

    Signed-off-by: Simon Glass
    Reviewed-by: Tom Rini
    [trini: Rework Kconfig logic slightly, define EEPROM location on TI eval
    platforms]
    Signed-off-by: Tom Rini

    Simon Glass
     
  • Commit 94e3c8c4fd7b ("crypto/fsl - Add progressive hashing support
    using hardware acceleration.") created entries for CONFIG_SHA1,
    CONFIG_SHA256, CONFIG_SHA_HW_ACCEL, and CONFIG_SHA_PROG_HW_ACCEL.
    However, no defconfig has migrated to it. Complete the move by first
    adding additional logic to various Kconfig files to select this when
    required and then use the moveconfig tool. In many cases we can select
    these because they are required to implement other drivers. We also
    correct how we include the various hashing algorithms in SPL.

    This commit was generated as follows (after Kconfig additions):

    [1] tools/moveconfig.py -y SHA1 SHA256 SHA_HW_ACCEL
    [2] tools/moveconfig.py -y SHA_PROG_HW_ACCEL

    Note:
    We cannot move SHA_HW_ACCEL and SHA_PROG_HW_ACCEL simultaneously
    because there is dependency between them.

    Cc: Poonam Aggrwal
    Cc: Naveen Burmi
    Cc: Po Liu
    Cc: Shengzhou Liu
    Cc: Priyanka Jain
    Cc: Shaohui Xie
    Cc: Chunhe Lan
    Cc: Chander Kashyap
    Cc: Steve Rae
    Cc: Dirk Eibach
    Cc: Feng Li
    Cc: Alison Wang
    Cc: Sumit Garg
    Cc: Mingkai Hu
    Cc: York Sun
    Cc: Prabhakar Kushwaha
    Cc: Jaehoon Chung
    Cc: Akshay Saraswat
    Cc: Heiko Schocher
    Cc: Jagan Teki
    Signed-off-by: Tom Rini
    Reviewed-by: Simon Glass
    Signed-off-by: Tom Rini

    Tom Rini
     

28 Jan, 2017

1 commit


26 Jan, 2017

1 commit


28 Oct, 2016

1 commit


24 Oct, 2016

1 commit


12 Oct, 2016

1 commit


20 Sep, 2016

1 commit


02 Jul, 2016

1 commit

  • As the help message of CONFIG_BOOTDELAY says, CONFIG_BOOTDELAY=-2
    means the autoboot with no delay, with no abort check even if
    CONFIG_ZERO_BOOTDELAY_CHECK is defined.

    To sum up, the autoboot behaves as follows:

    [1] CONFIG_BOOTDELAY=0 && CONFIG_ZERO_BOOTDELAY_CHECK=y
    autoboot with no delay, but you can abort it by key input

    [2] CONFIG_BOOTDELAY=0 && CONFIG_ZERO_BOOTDELAY_CHECK=n
    autoboot with no delay, with no check for abort

    [3] CONFIG_BOOTDELAY=-1
    disable autoboot

    [4] CONFIG_BOOTDELAY=-2
    autoboot with no delay, with no check for abort

    As you notice, [2] and [4] come to the same result, which means we
    do not need CONFIG_ZERO_BOOTDELAY_CHECK. We can control all the
    cases only by CONFIG_BOOTDELAY, like this:

    [1] CONFIG_BOOTDELAY=0
    autoboot with no delay, but you can abort it by key input

    [2] CONFIG_BOOTDELAY=-1
    disable autoboot

    [3] CONFIG_BOOTDELAY=-2
    autoboot with no delay, with no check for abort

    This commit converts the logic as follow:
    CONFIG_BOOTDELAY=0 && CONFIG_ZERO_BOOTDELAY_CHECK=n
    --> CONFIG_BOOTDELAY=-2

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Stefan Roese
    Acked-by: Igor Grinberg
    Reviewed-by: Simon Glass
    Acked-by: Vladimir Zapolskiy
    Reviewed-by: Heiko Schocher
    Acked-by: Christian Riesch
    Acked-by: Hannes Schmelzer

    Masahiro Yamada
     

17 Jun, 2016

1 commit


26 Apr, 2016

1 commit


22 Nov, 2015

1 commit


19 Nov, 2015

1 commit


23 Oct, 2015

1 commit


31 Aug, 2015

1 commit


26 Jun, 2015

1 commit


01 Jun, 2015

1 commit


13 May, 2015

1 commit

  • In order to reduce merge conflicts and to maintain the simplest possible
    defconfig files, we should be using the savedefconfig feature of Kconfig
    every time a new feature is added. This keeps the defconfig settings to
    a minimum (only those things not default) and keeps them in the same
    order as the Kconfig options.

    Signed-off-by: Joe Hershberger
    Cc: Masahiro Yamada
    Acked-by: Stephen Warren
    Cc: Tom Rini

    Joe Hershberger
     

25 Sep, 2014

1 commit

  • CONFIG_CMD_BOOTM is defined in config_cmd_defaults.h
    which is forcebly included from each board.
    So, the default value of "config CMD_BOOTM" should be "y".

    For some boards undefining it (bf506f-ezkit, controlcenterd_TRAILBLA,
    controlcenterd_TRAILBLAZER_DEVELOP, controlcenterd_TRAILBLAZER),
    "# CONFIG_CMD_BOOTM is not set" should be added to their defconfig.

    Signed-off-by: Masahiro Yamada
    Acked-by: Simon Glass

    Masahiro Yamada
     

30 Jul, 2014

1 commit

  • This commit adds:
    - arch/${ARCH}/Kconfig
    provide a menu to select target boards
    - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
    set CONFIG macros to the appropriate values for each board
    - configs/${TARGET_BOARD}_defconfig
    default setting of each board

    (This commit was automatically generated by a conversion script
    based on boards.cfg)

    In Linux Kernel, defconfig files are located under
    arch/${ARCH}/configs/ directory.
    It works in Linux Kernel since ARCH is always given from the
    command line for cross compile.

    But in U-Boot, ARCH is not given from the command line.
    Which means we cannot know ARCH until the board configuration is done.
    That is why all the "*_defconfig" files should be gathered into a
    single directory ./configs/.

    Signed-off-by: Masahiro Yamada
    Acked-by: Simon Glass

    Masahiro Yamada