29 Feb, 2020

1 commit


23 Jan, 2020

1 commit


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
     

13 Nov, 2019

1 commit


26 Aug, 2019

1 commit


02 Aug, 2019

1 commit

  • This converts the following to Kconfig:
    CONFIG_USE_PREBOOT
    CONFIG_PREBOOT

    Both are together in one commit, since otherwise the former causes kconfig
    to define the latter, which gives duplicate symbol errors.

    Includes a manual fixup for CONFIG_PREBOOT in ids8313_defconfig since the
    backslash lands in the wrong place. Similarly with socfpga_vining_fpga.

    Signed-off-by: Simon Glass

    Simon Glass
     

09 Jul, 2019

1 commit

  • Enable the extended ENV options for AT91 and OMAP2PLUS in order to be
    able to use CONFIG_ENV_UBI_* on these architectures.

    As this change also makes the configs ENV_SIZE, ENV_SECT_SIZE,
    ENV_OFFSET visible to AT91 and OMAP2PLUS, migrate users of these to
    KConfig.

    This migration was run using an extended moveconfig.py which evaluates
    expressions such as "(512 << 10)". See patch ("moveconfig: expand
    simple expressions").

    All modified boards were built with SOURCE_DATE_EPOCH=0 before and
    after the change and successfully confirmed that the identical binary
    is generated (the only exception was igep00x0, which does not define
    CONFIG_ENV_IS_IN_UBI in the original board header. Once that is
    defined, the test passes too).

    hs: rebased patch to:
    68b90e57bc: "configs: tinker-rk3288 disable CONFIG_SPL_I2C_SUPPORT"

    Signed-off-by: Markus Klotzbuecher
    Cc: Heiko Schocher
    Cc: Eugen Hristev
    Cc: Tom Rini

    Markus Klotzbuecher
     

30 Apr, 2019

1 commit


19 Apr, 2019

1 commit

  • USB_MUSB_TI requires USB_MUSB_DSPS, failing at link time if it's not
    selected:

    drivers/usb/musb-new/built-in.o: In function `ti_musb_host_ofdata_to_platdata':
    drivers/usb/musb-new/ti-musb.c:193: undefined reference to `musb_dsps_ops'

    or if OF_CONTROL is not selected:

    arch/arm/mach-omap2/built-in.o:(.data.usb0+0x24): undefined reference to `musb_dsps_ops'

    Reviewed-by: Hannes Schmelzer
    Tested-by: Hannes Schmelzer
    Signed-off-by: Alex Kiernan

    Alex Kiernan
     

19 Feb, 2019

1 commit


09 Feb, 2019

1 commit


08 Jan, 2019

1 commit


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

08 Aug, 2018

1 commit


20 Jul, 2018

3 commits

  • - add a devicetree for each variant (mmc, spi, nand)
    - drop unneeded code from board and bur/common
    - drop unneeded stuff from config header files
    - minor adaptions to be compliant with driver model (requesting gpio,..)
    - harmonize the commandset over all brppt1 targets

    Signed-off-by: Hannes Schmelzer

    Hannes Schmelzer
     
  • With this commit we do:

    - set the bootdelay in all brppt1 defconfigs to 0, this makes
    development easier, since we can break into serial console.

    - move CONFIG_BOOTCOMMAND from header file to defconfig

    - introduce b_mode variable for selecting the final boot-target.
    This b_mode represents the boot-switch, which can found on most b&r
    targets. On the brppt1 this boot-switch is derived from some gpio and
    the bootcounter within the RTC block, making it so possible to force
    a boot-target (as example for repair-case).

    - refactor the environment for booting new flexible way
    primary we want to get some bootscr.img within the mass-storage,
    this script then loads everything needed for the boot.
    For legacy reason we implement the t30lgcy#x boot targets, booting the
    already delivered linux-images.

    - make space for the cfgscr within mtdparts on brppt1_nand

    Signed-off-by: Hannes Schmelzer

    Hannes Schmelzer
     
  • On this linux target long time ago the OS is using DRM driver for
    handling video output, the pre initialization of u-boot and the display
    summary screen is obsolete. With this patch we drop the LCD-support from
    thisd board.

    Signed-off-by: Hannes Schmelzer

    Hannes Schmelzer
     

04 Jun, 2018

1 commit


17 Apr, 2018

1 commit


09 Apr, 2018

1 commit


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

15 Feb, 2018

1 commit


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
     

15 May, 2017

1 commit

  • Move this entry to Kconfig. As it is a hardware watchdog, select
    HW_WATCHDOG. While we could default to enabling this for all platforms,
    it is currently only enabled by default on AM33XX, so keep that logic
    today.

    Cc: Roger Meier
    Signed-off-by: Tom Rini

    Tom Rini
     

01 May, 2017

1 commit