05 Dec, 2019

1 commit


21 Nov, 2019

2 commits

  • - 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
     
  • Today in initr_reloc_global_data() we use some non-obvious tests to
    determine if we need to relocate the env_addr within gd or not. In
    order to facilitate migration of other symbols to Kconfig we need to
    introduce a new symbol for this particular use case.

    Cc: Wolfgang Denk
    Cc: Joe Hershberger
    Signed-off-by: Tom Rini

    Tom Rini
     

08 Oct, 2019

1 commit


24 Aug, 2019

1 commit


23 Jun, 2019

1 commit


05 May, 2019

1 commit

  • This converts the following to Kconfig:
    CONFIG_SUPPORT_EMMC_BOOT

    As requested by Michal Simek , these boards
    have no eMMC so CONFIG_SUPPORT_EMMC_BOOT has not been migrated:

    xilinx_zynqmp_zc1275_revB
    xilinx_zynqmp_zc1751_xm018_dc4
    xilinx_zynqmp_zc1751_xm019_dc5
    xilinx_zynqmp_zcu100_revC
    xilinx_zynqmp_zcu102_rev1_0
    xilinx_zynqmp_zcu102_revA
    xilinx_zynqmp_zcu102_revB
    xilinx_zynqmp_zcu104_revA
    xilinx_zynqmp_zcu104_revC
    xilinx_zynqmp_zcu106_revA
    xilinx_zynqmp_zcu111_revA

    Signed-off-by: Alex Kiernan
    Acked-by: Lukasz Majewski
    Acked-by: Patrick Delaunay
    Acked-by: Ramon Fried
    Reviewed-by: Andy Shevchenko
    Tested-by: Sébastien Szymanski

    Alex Kiernan
     

30 Apr, 2019

1 commit


19 Jan, 2019

1 commit

  • The bounce buffer is used by a few drivers (most of the MMC drivers)
    to overcome limitations in their respective DMA implementation.

    This moves the configuration to Kconfig and makes it user-selectable
    (even though it will be a required feature to make those drivers
    work): the expected usage is for drivers depending on this to 'select'
    it unconditionally from their respective Kconfig (see follow-up
    patches).

    This commit includes a full migration using moveconfig.py to ensure
    that each commit compiles. To ensure bisectability we update
    dependencies of various drivers to now select BOUNCE_BUFFER when needed.

    [trini: Squash all patches to ensure bisectability]
    Signed-off-by: Tom Rini
    Signed-off-by: Philipp Tomsich
    Reviewed-by: Otavio Salvador [dw_mmc portion]
    Reviewed-by: Fabio Estevam [mxsmmc portion]
    Reviewed-by: Simon Glass [tegra portion]

    Philipp Tomsich
     

22 Oct, 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
     

09 Apr, 2018

1 commit


28 Feb, 2018

1 commit


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
     

29 Dec, 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

1 commit

  • The g_dnl USB settings for the vendor ID, product ID and manufacturer are
    actually common settings that can and should be shared by all the gadgets.

    Make them common by renaming them, and convert all the users.

    Reviewed-by: Simon Glass
    Reviewed-by: Lukasz Majewski
    Signed-off-by: Maxime Ripard

    Maxime Ripard
     

28 Aug, 2017

1 commit


15 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
     

12 Jul, 2017

1 commit

  • warp can run different kernel versions, such as NXP 4.1 or
    mainline.

    Currently the rootfs location is passed via mmcblk number and the
    problem with this approach is that the mmcblk number for the eMMC
    changes depending on the kernel version.

    In order to avoid such issue, use UUID method to specify the rootfs
    location.

    Succesfully tested booting a NXP 4.1 and also a mainline 4.12 kernel.

    Signed-off-by: Fabio Estevam
    Acked-by: Otavio Salvador

    Fabio Estevam
     

30 Apr, 2017

1 commit


26 Jan, 2017

1 commit


24 Jan, 2017

1 commit


22 Jan, 2017

1 commit


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

1 commit


07 Sep, 2016

1 commit

  • Since commit a13d3757f7df ("warp: Use imx_ddr_size() for calculating the
    DDR size") warp board no longer boots.

    The reason for the breakage is that the warp board is using the DDR
    configuration from mx6slevk. A fundamental difference between warp and
    mx6slevk is that warp only uses one DDR chip select while mx6slevk uses two.

    The imx_ddr() function calculates the RAM size in runtime by reading the
    values of registers MDCTL and MDMISC.

    So in order to fix this warp boot issue, create a imximage DDR file specific
    to warp, where the MDCTL register is configured to only activates a single
    chip select.

    Reported-by: Breno Lima
    Signed-off-by: Fabio Estevam
    Tested-by: Breno Lima

    Fabio Estevam
     

17 Jun, 2016

1 commit


26 Apr, 2016

3 commits


20 Apr, 2016

3 commits


26 Mar, 2016

1 commit

  • The description was borrowed from kernel. "tristate" type was changed
    to "bool" (I believe we don't support modules for u-boot yet, right?).
    CONFIG_USB_GADGET requires CONFIG_USB to be defined too, so add it along
    as well.

    Definitions were added to defconfig files in a way that
    "make savedefconfig" generates exactly the same file as used defconfig.

    Signed-off-by: Sam Protsenko
    [trini: Add zynq_zc702 conversion]
    Signed-off-by: Tom Rini

    Sam Protsenko
     

15 Mar, 2016

1 commit


19 Nov, 2015

1 commit


02 Sep, 2015

1 commit

  • Move TARGET_xx Kconfig option based on mx6 to arch/arm/cpu/armv7/mx6/Kconfig.
    Add enable "CONFIG_ARCH_MX6" for boards based on mx6.
    Then we can choose target boards using "make ARCH=arm menuconfig"
    with ARCH_MX6 defined.

    If using original way, we have no chance to enable ARCH_MX6 when
    "make menuconfig". Even define CONFIG_ARCH_MX6=y in xx_defconfig,
    kconfig will complains "arch/../configs/platinum_titanium_defconfig:3:
    warning: override: TARGET_PLATINUM_TITANIUM changes choice state"

    Signed-off-by: Peng Fan
    Cc: Stefano Babic
    Cc: Heiko Schocher
    Cc: Tim Harvey
    Cc: Eric Bénard
    Cc: Fabio Estevam
    Cc: Eric Nelson
    Cc: Marek Vasut
    Cc: Christian Gmeiner
    Cc: Stefan Roese
    Cc: Soeren Moch
    Cc: Otavio Salvador
    Acked-by: Stefano Babic
    Acked-by: Soeren Moch
    Acked-by: Otavio Salvador
    Acked-by: Christian Gmeiner

    Peng Fan