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
     

04 Sep, 2017

2 commits


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

2 commits

  • This converts the following to Kconfig:
    CONFIG_ENV_IS_IN_DATAFLASH

    Signed-off-by: Simon Glass

    Simon Glass
     
  • 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
     

20 Mar, 2017

1 commit


13 Feb, 2017

1 commit

  • We repeated partial moves for CONFIG_SYS_NO_FLASH, but this is
    not completed. Finish this work by the tool.

    During this move, let's rename it to CONFIG_MTD_NOR_FLASH.
    Actually, we have more instances of "#ifndef CONFIG_SYS_NO_FLASH"
    than those of "#ifdef CONFIG_SYS_NO_FLASH". Flipping the logic will
    make the code more readable. Besides, negative meaning symbols do
    not fit in obj-$(CONFIG_...) style Makefiles.

    This commit was created as follows:

    [1] Edit "default n" to "default y" in the config entry in
    common/Kconfig.

    [2] Run "tools/moveconfig.py -y -r HEAD SYS_NO_FLASH"

    [3] Rename the instances in defconfigs by the following:
    find . -path './configs/*_defconfig' | xargs sed -i \
    -e '/CONFIG_SYS_NO_FLASH=y/d' \
    -e 's/# CONFIG_SYS_NO_FLASH is not set/CONFIG_MTD_NOR_FLASH=y/'

    [4] Change the conditionals by the following:
    find . -name '*.[ch]' | xargs sed -i \
    -e 's/ifndef CONFIG_SYS_NO_FLASH/ifdef CONFIG_MTD_NOR_FLASH/' \
    -e 's/ifdef CONFIG_SYS_NO_FLASH/ifndef CONFIG_MTD_NOR_FLASH/' \
    -e 's/!defined(CONFIG_SYS_NO_FLASH)/defined(CONFIG_MTD_NOR_FLASH)/' \
    -e 's/defined(CONFIG_SYS_NO_FLASH)/!defined(CONFIG_MTD_NOR_FLASH)/'

    [5] Modify the following manually
    - Rename the rest of instances
    - Remove the description from README
    - Create the new Kconfig entry in drivers/mtd/Kconfig
    - Remove the old Kconfig entry from common/Kconfig
    - Remove the garbage comments from include/configs/*.h

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

29 Jan, 2017

1 commit


26 Jan, 2017

1 commit


12 Oct, 2016

2 commits


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
     

10 Jun, 2016

1 commit


26 Apr, 2016

4 commits


15 Mar, 2016

2 commits

  • There are already two FIT options in Kconfig but the CONFIG options are
    still in the header files. We need to do a proper move to fix this.

    Move these options to Kconfig and tidy up board configuration:

    CONFIG_FIT
    CONFIG_OF_BOARD_SETUP
    CONFIG_OF_SYSTEM_SETUP
    CONFIG_FIT_SIGNATURE
    CONFIG_FIT_BEST_MATCH
    CONFIG_FIT_VERBOSE
    CONFIG_OF_STDOUT_VIA_ALIAS
    CONFIG_RSA

    Unfortunately the first one is a little complicated. We need to make sure
    this option is not enabled in SPL by this change. Also this option is
    enabled automatically in the host builds by defining CONFIG_FIT in the
    image.h file. To solve this, add a new IMAGE_USE_FIT #define which can
    be used in files that are built on the host but must also build for U-Boot
    and SPL.

    Note: Masahiro's moveconfig.py script is amazing.

    Signed-off-by: Simon Glass
    [trini: Add microblaze change, various configs/ re-applies]
    Signed-off-by: Tom Rini

    Simon Glass
     
  • Move this option to Kconfig and tidy up existing boards.

    Signed-off-by: Simon Glass

    Simon Glass
     

03 Nov, 2015

1 commit


25 Oct, 2015

1 commit

  • We have finished Generic Board conversion for ARM and PowerPC, i.e.
    all the boards have been converted except OpenRISC, SuperH, SPARC,
    which have not supported Generic Board framework yet.

    Select SYS_GENERIC_BOARD in arch/Kconfig and delete all the macro
    defines in include/configs/*.h.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

11 Sep, 2015

1 commit


26 Jun, 2015

1 commit


17 Nov, 2014

1 commit


09 Dec, 2013

1 commit


10 Nov, 2013

1 commit

  • Conflicts:
    arch/arm/cpu/arm926ejs/mxs/Makefile
    board/compulab/cm_t35/Makefile
    board/corscience/tricorder/Makefile
    board/ppcag/bg0900/Makefile
    drivers/bootcount/Makefile
    include/configs/omap4_common.h
    include/configs/pdnb3.h

    Makefile conflicts are due to additions/removals of
    object files on the ARM branch vs KBuild introduction
    on the main branch. Resolution consists in adjusting
    the list of object files in the main branch version.
    This also applies to two files which are not listed
    as conflicting but had to be modified:

    board/compulab/common/Makefile
    board/udoo/Makefile

    include/configs/omap4_common.h conflicts are due to
    the OMAP4 conversion to ti_armv7_common.h on the ARM
    side, and CONFIG_SYS_HZ removal on the main side.
    Resolution is to convert as this icludes removal of
    CONFIG_SYS_HZ.

    include/configs/pdnb3.h is due to a removal on ARM side.
    Trivial resolution is to remove the file.

    Note: 'git show' will also list two files just because
    they are new:

    include/configs/am335x_igep0033.h
    include/configs/omap3_igep00x0.h

    Albert ARIBAUD
     

05 Nov, 2013

3 commits


24 Jul, 2013

1 commit


01 Sep, 2012

1 commit


21 Jun, 2012

1 commit


15 May, 2012

1 commit


29 Nov, 2011

1 commit


05 Nov, 2011

1 commit

  • quotation from Albert ARIBAUD:
    "Recently the ARM mach-types.h file has been brought in sync with its
    Linux original, leasing to a number of boards not being listed any more,
    as the new list only contains boards which have actual Linux support or
    were declared less than one year ago.

    The symptom is a build failure with a message of the form "error:
    'MACH_TYPE_XXXXXX' undeclared (first use in this function)".

    U-Boot maintainers of such boards (in Cc: of this mail) should provide a
    patch to re-introduce the MACH_TYPE_XXXXXX definition in their boards'
    config header file in include/configs/."

    Signed-off-by: Daniel Gorsulowski

    Daniel Gorsulowski
     

06 Oct, 2011

1 commit


04 Sep, 2011

1 commit