22 Feb, 2019

1 commit


19 Feb, 2019

1 commit


16 Jan, 2019

1 commit


08 Jan, 2019

1 commit


14 Nov, 2018

1 commit

  • Now that CMD_UBI does not select CMD_MTDPARTS we need to make platforms
    that had been enabling it turn it on by hand. This exposed that we had
    not yet migrated CMD_MTDPARTS fully, so do so now.

    Fixes: 86dfa556d927 ("cmd: ubi: Remove useless call to mtdparts_init()")
    Signed-off-by: Tom Rini

    Tom Rini
     

04 Sep, 2018

1 commit


18 Aug, 2018

1 commit


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
     

23 Jul, 2018

1 commit


16 Mar, 2018

1 commit

  • This converts the following to Kconfig:
    CONFIG_CONS_INDEX

    We have existing entries for this option in a number of places, with
    different guards on them. They're also sometimes used for things not
    directly inside of the serial driver. First, introduce a new symbol to
    guard the use of CONFIG_CONS_INDEX, so that in the case where we don't
    need this for the serial driver, but for some other use, we can still do
    it. Next, consolidate all of these into the single entry in
    drivers/serial/Kconfig. Finally, introduce CONS_INDEX_[023456] so that
    we can imply a correct value here to make the defconfig side of this
    smaller.

    Signed-off-by: Adam Ford
    [trini: Rework a lot of the logic here, such that I took authorship from
    Adam, but kept his S-o-B line]
    Signed-off-by: Tom Rini

    Tom Rini
     

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
     

17 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
     

08 Sep, 2017

2 commits


28 Aug, 2017

1 commit


15 Aug, 2017

2 commits


31 Jul, 2017

1 commit


26 Jul, 2017

1 commit


11 Jul, 2017

1 commit


10 Jul, 2017

1 commit


07 Jul, 2017

1 commit


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
     

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


11 Jan, 2017

2 commits

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

    CONFIG_EXYNOS_DWMMC (renamed to CONFIG_MMC_DW_EXYNOS)
    CONFIG_HIKEY_DWMMC (renamed to CONFIG_MMC_DW_K3)
    CONFIG_SOCFPGA_DWMMC (renamed to CONFIG_MMC_DW_SOCFPGA)

    The "HIKEY" is a board name, so it is not suitable for the MMC
    controller name. I am following the name used in Linux.

    This commit was generated as follows:

    [1] Rename the config options with the following command:
    find . -name .git -prune -o ! -path ./scripts/config_whitelist.txt \
    -type f -print | xargs sed -i -e '
    s/CONFIG_EXYNOS_DWMMC/CONFIG_MMC_DW_EXYNOS/g
    s/CONFIG_HIKEY_DWMMC/CONFIG_MMC_DW_K3/g
    s/CONFIG_SOCFPGA_DWMMC/CONFIG_MMC_DW_SOCFPGA/g
    '

    [2] Commit the changes

    [3] Create the entries in drivers/mmc/Kconfig
    (with default y for EXYNOS and SOCFPGA)

    [4] Run the following:
    tools/moveconfig.py -y -r HEAD MMC_DW_EXYNOS MMC_DW_K3 MMC_DW_SOCFPGA

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

    [6] Clean-up doc/README.socfpga by hand

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

    Masahiro Yamada
     
  • This commit was created as follows:

    [1] Rename the option with the following command:
    find . -name .git -prune -o ! -path ./scripts/config_whitelist.txt \
    -type f -print | xargs sed -i -e 's/CONFIG_DWMMC/CONFIG_MMC_DW/g'

    [2] create the entry for MMC_DW in drivers/mmc/Kconfig
    (the prompt and help were copied from Linux)

    [3] run "tools/moveconfig.py -y MMC_DW"

    [4] add "depends on MMC_DW" to the MMC_DW_ROCKCHIP entry

    [5] Clean-up doc/README.socfpga by hand

    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
     

12 Oct, 2016

2 commits


20 Sep, 2016

1 commit


10 Sep, 2016

1 commit


09 Sep, 2016

1 commit


17 Jun, 2016

1 commit


10 Jun, 2016

1 commit


26 Apr, 2016

4 commits