28 Mar, 2020

1 commit


27 Mar, 2020

1 commit


24 Mar, 2020

1 commit


23 Jan, 2020

1 commit


04 Dec, 2019

1 commit


21 Nov, 2019

1 commit

  • - In ARMv8 NXP Layerscape platforms we also need to make use of
    CONFIG_SYS_RELOC_GD_ENV_ADDR now, do so.
    - On ENV_IS_IN_REMOTE, CONFIG_ENV_OFFSET is never used, drop the define
    to 0.
    - Add Kconfig entry for ENV_ADDR.
    - Make ENV_ADDR / ENV_OFFSET depend on the env locations that use it.
    - Add ENV_xxx_REDUND options that depend on their primary option and
    SYS_REDUNDAND_ENVIRONMENT
    - On a number of PowerPC platforms, use SPL_ENV_ADDR not CONFIG_ENV_ADDR
    for the pre-main-U-Boot environment location.
    - On ENV_IS_IN_SPI_FLASH, check not for CONFIG_ENV_ADDR being set but
    rather it being non-zero, as it will now be zero by default.
    - Rework the env_offset absolute in env/embedded.o to not use
    CONFIG_ENV_OFFSET as it was the only use of ENV_OFFSET within
    ENV_IS_IN_FLASH.
    - Migrate all platforms.

    Cc: Wolfgang Denk
    Cc: Joe Hershberger
    Cc: Patrick Delaunay
    Cc: uboot-stm32@st-md-mailman.stormreply.com
    Signed-off-by: Tom Rini
    Acked-by: Joe Hershberger
    Reviewed-by: Simon Goldschmidt

    Tom Rini
     

30 Apr, 2019

1 commit


23 Apr, 2019

1 commit

  • vexpress_ca15_tc2_defconfig and vexpress_ca9x4_defconfig do not provide
    device trees (as $fdtcontroladdr) as needed to pass our Travis CI tests.

    As we are on the move to requiring block devices to be based on the driver
    model these boards either will have to be converted to use device trees or
    will be kicked out of U-Boot.

    So let's disable CONFIG_EFI_LOADER on these boards until the device tree
    issue is resolved.

    Signed-off-by: Heinrich Schuchardt

    Heinrich Schuchardt
     

27 Nov, 2018

1 commit

  • This allow for convenient use of QEMU machine to test loading of UBI
    filesystem. There are a couple of changes made together of this which
    are required:

    1) The malloc must be at least 512 KiB to allow the use of UBI
    filesystem. We are going to enable it in a next patch.

    2) MTD_DEVICE must be enabled, otherwise we get missing symbols
    during the build

    Following configs were change:

    - vexpress_aemv8a_dram_defconfig
    - vexpress_aemv8a_juno_defconfig
    - vexpress_aemv8a_semi_defconfig
    - vexpress_ca15_tc2_defconfig
    - vexpress_ca5x2_defconfig
    - vexpress_ca9x4_defconfig

    Signed-off-by: Otavio Salvador
    Acked-by: Liviu Dudau

    Otavio Salvador
     

20 Oct, 2018

1 commit


04 Sep, 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
     

28 Apr, 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
     

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
     

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
     

21 Oct, 2017

1 commit

  • We add the various SMC91XX symbols to drivers/net/Kconfig and then this
    converts the following to Kconfig:
    CONFIG_SMC911X
    CONFIG_SMC911X_BASE
    CONFIG_SMC911X_16_BIT
    CONFIG_SMC911X_32_BIT

    Signed-off-by: Adam Ford
    [trini: Apply to the rest of the tree, re-squash old and new patch]
    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


26 Jul, 2017

1 commit


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
     

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


09 Sep, 2016

1 commit


17 Jun, 2016

1 commit


10 Jun, 2016

1 commit


27 May, 2016

1 commit

  • We have a bunch of boards that define their vendor class identifier and
    client archs in the board files or in the distro config. Move everything
    to the generic Kconfig options.

    We're missing the distinction between i386 and x86_64, as I couldn't find
    any config variable that would tell us the difference. Is that really important
    to people? I guess not, so I left it out.

    Signed-off-by: Alexander Graf
    Reviewed-by: Tom Rini

    Alexander Graf
     

26 Apr, 2016

3 commits


15 Mar, 2016

1 commit


26 Jun, 2015

1 commit


01 Jun, 2015

1 commit


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