23 Jan, 2018

1 commit


19 Dec, 2017

1 commit


18 Nov, 2017

1 commit

  • We first introduce CONFIG_USE_BOOTCOMMAND, similar to
    CONFIG_USE_BOOTARGS. We then migrate CONFIG_BOOTCOMMAND for most
    CONFIG_DISTRO_DEFAULT users. In some cases platforms have a complex
    scheme around this usage, and these have been defered for the moment so
    that platform maintainers can work on a migration plan.

    Signed-off-by: Tom Rini
    Reviewed-by: Lukasz Majewski

    Tom Rini
     

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

4 commits


02 Sep, 2017

1 commit


28 Aug, 2017

1 commit


14 Aug, 2017

1 commit


08 Aug, 2017

1 commit


05 Aug, 2017

1 commit


01 Aug, 2017

1 commit


26 Jul, 2017

1 commit


25 Jul, 2017

1 commit


12 Jul, 2017

1 commit

  • When CONFIG_CMD_FASTBOOT or CONFIG_USB_FUNCTION_FASTBOOT are defined
    in am335x_evm.h, a dependency on g_dnl.c is created. This in turn
    creates a dependency on having USB gadget enabled.
    As a result we can't create configs with USB gadget disabled.

    Since these CONFIG_ variables are now part of kconfig, move them to
    the board defconfigs, and out of am335x_evm.h. This both preserves
    current defaults, and allows creating configs with USB gadget off.

    Signed-off-by: Alexandru Gagniuc
    Reviewed-by: Tom Rini

    Alexandru Gagniuc
     

07 Jul, 2017

1 commit


19 Jun, 2017

1 commit


09 May, 2017

1 commit


28 Apr, 2017

2 commits


19 Mar, 2017

1 commit

  • Today, we have cases where we wish to build all of U-Boot in Thumb2 mode for
    various reasons. We also have cases where we only build SPL in Thumb2 mode due
    to size constraints and wish to build the rest of the system in ARM mode. So
    in this migration we introduce a new symbol as well, SPL_SYS_THUMB_BUILD to
    control if we build everything or just SPL (or in theory, just U-Boot) in
    Thumb2 mode.

    Signed-off-by: Tom Rini
    Acked-by: Siarhei Siamashka

    Tom Rini
     

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
     

28 Jan, 2017

1 commit


26 Jan, 2017

2 commits


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
     

04 Dec, 2016

1 commit

  • A number of platforms had been using the distro default feature before
    it was moved to Kconfig but did not enable the new Kconfig option when
    it was enabled. This caused a regression in terms of features and this
    introduces breakage when more things move to Kconfig.

    Signed-off-by: Tom Rini

    Tom Rini
     

24 Oct, 2016

1 commit


02 Oct, 2016

1 commit

  • The config option AM33XX is used in several boards and should be
    defined as a stand-alone option for this SOC. We break this out
    from target boards that use this SoC and common headers then enable
    AM33XX on in all the boards that used these targets to eliminate any
    functional change with this patch.

    This is similar to what has already been done in
    9de852642cae ("arm: Kconfig: Add support for AM43xx SoC specific Kconfig")
    and is done for the same reasons.

    Signed-off-by: Andrew F. Davis
    Acked-by: Lokesh Vutla
    Reviewed-by: Tom Rini

    Andrew F. Davis
     

27 Sep, 2016

1 commit

  • Introduce a hidden USB_FUNCTION_DFU Kconfig option and select it for
    CMD_DFU (as we must have the DFU command enabled to do anything DFU).
    Make all of the entries in drivers/dfu/Kconfig depend on CMD_DFU and add
    options for all of the back end choices that DFU can make use of.

    Cc: Lukasz Majewski
    Signed-off-by: Tom Rini
    Acked-by: Lukasz Majewski

    Tom Rini
     

10 Sep, 2016

2 commits


09 Sep, 2016

1 commit


17 Jun, 2016

1 commit


10 Jun, 2016

1 commit