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
     

06 Feb, 2018

1 commit

  • cmd/Makefile has:

    ifdef CONFIG_FPGA
    obj-$(CONFIG_CMD_FPGA) += fpga.o
    endif

    which means that if CONFIG_FPGA is not set, CONFIG_CMD_FPGA silently
    does nothing. Let's remove that Makefile conditional and instead express
    this equivalent dependency in Kconfig, so a lot of redundant

    # CONFIG_CMD_FPGA is not set

    can be removed from board defconfigs that don't actually have an FPGA.

    Signed-off-by: Tuomas Tynkkynen

    Tuomas Tynkkynen
     

23 Jan, 2018

1 commit


21 Oct, 2017

1 commit

  • This converts the following to Kconfig:
    CONFIG_NAND_MXC
    CONFIG_NAND_OMAP_GPMC
    CONFIG_NAND_OMAP_GPMC_PREFETCH
    CONFIG_NAND_OMAP_ELM
    CONFIG_SPL_NAND_AM33XX_BCH
    CONFIG_SPL_NAND_SIMPLE
    CONFIG_SYS_NAND_BUSWIDTH_16BIT

    Signed-off-by: Adam Ford
    Reviewed-by: Heiko Schocher
    [trini: Finish migration of CONFIG_SPL_NAND_SIMPLE, fix some build issues,
    add CONFIG_NAND_MXC so we can do CONFIG_SYS_NAND_BUSWIDTH_16BIT]
    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
     

28 Aug, 2017

1 commit


15 Aug, 2017

1 commit


08 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
     

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
     

04 Jun, 2017

1 commit

  • Now that these symbols are in Kconfig, migrate all users. Use imply on
    a number of platforms that default to having this enabled. As part of
    this we must migrate some straglers for CMD_FAT and DOS_PARTITION.

    Signed-off-by: Tom Rini

    Tom Rini
     

01 May, 2017

1 commit


30 Apr, 2017

1 commit


28 Apr, 2017

1 commit


14 Mar, 2017

1 commit


09 Feb, 2017

1 commit

  • CONFIG_CMD_ZIP is not defined by any board. I am moving
    CONFIG_CMD_UNZIP to defconfig files except UniPhier SoC family.

    I am the maintainer of UniPhier platform, so I know "select CMD_UNZIP"
    is better for this platform.

    Signed-off-by: Masahiro Yamada
    Acked-by: Michal Simek
    Acked-by: Stefan Roese
    Acked-by: Ryan Harkin
    Tested-by: Ryan Harkin

    Masahiro Yamada
     

26 Jan, 2017

1 commit


24 Jan, 2017

1 commit


22 Jan, 2017

1 commit


11 Jan, 2017

1 commit

  • Move (and rename) the following CONFIG options to Kconfig:

    CONFIG_DAVINCI_MMC (renamed to CONFIG_MMC_DAVINCI)
    CONFIG_OMAP_HSMMC (renamed to CONFIG_MMC_OMAP_HS)
    CONFIG_MXC_MMC (renamed to CONFIG_MMC_MXC)
    CONFIG_MXS_MMC (renamed to CONFIG_MMC_MXS)
    CONFIG_TEGRA_MMC (renamed to CONFIG_MMC_SDHCI_TEGRA)
    CONFIG_SUNXI_MMC (renamed to CONFIG_MMC_SUNXI)

    They are the same option names as used in Linux.

    This commit was created as follows:

    [1] Rename the options with the following command:

    find . -name .git -prune -o ! -path ./scripts/config_whitelist.txt \
    -type f -print | xargs sed -i -e '
    s/CONFIG_DAVINCI_MMC/CONFIG_MMC_DAVINCI/g
    s/CONFIG_OMAP_HSMMC/CONFIG_MMC_OMAP_HS/g
    s/CONFIG_MXC_MMC/CONFIG_MMC_MXC/g
    s/CONFIG_MXS_MMC/CONFIG_MMC_MXS/g
    s/CONFIG_TEGRA_MMC/CONFIG_MMC_SDHCI_TEGRA/g
    s/CONFIG_SUNXI_MMC/CONFIG_MMC_SUNXI/g
    '

    [2] Commit the changes

    [3] Create entries in driver/mmc/Kconfig.
    (copied from Linux)

    [4] Move the options with the following command
    tools/moveconfig.py -y -r HEAD \
    MMC_DAVINCI MMC_OMAP_HS MMC_MXC MMC_MXS MMC_SDHCI_TEGRA MMC_SUNXI

    [5] Sort and align drivers/mmc/Makefile for readability

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Marek Vasut

    Masahiro Yamada
     

19 Nov, 2016

1 commit


24 Oct, 2016

4 commits


12 Oct, 2016

2 commits


17 Sep, 2016

9 commits


10 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
     

25 Jun, 2016

1 commit