1. 25 Apr, 2018 1 commit
  2. 08 Apr, 2018 1 commit
  3. 11 Feb, 2018 1 commit
    • Tom Rini's avatar
      configs: Migrate CONFIG_SYS_TEXT_BASE · 278b90ce
      Tom Rini authored
      
      
      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's avatarTom Rini <trini@konsulko.com>
      278b90ce
  4. 18 Dec, 2017 1 commit
  5. 07 Nov, 2017 1 commit
  6. 10 Oct, 2017 1 commit
    • Tuomas Tynkkynen's avatar
      cmd: Toggle the default value of CONFIG_CMD_IMLS · ad12dc18
      Tuomas Tynkkynen authored and Tom Rini's avatar Tom Rini committed
      
      
      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: default avatarTuomas Tynkkynen <tuomas.tynkkynen@iki.fi>
      ad12dc18
  7. 08 Sep, 2017 2 commits
  8. 28 Aug, 2017 1 commit
  9. 07 Aug, 2017 1 commit
  10. 26 Jul, 2017 1 commit
    • Simon Glass's avatar
      Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig · 2be29653
      Simon Glass authored and Tom Rini's avatar Tom Rini committed
      
      
      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's avatarSimon Glass <sjg@chromium.org>
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      2be29653
  11. 19 Jun, 2017 1 commit
  12. 10 May, 2017 3 commits
  13. 01 May, 2017 1 commit
  14. 27 Apr, 2017 1 commit
  15. 15 Apr, 2017 2 commits
  16. 05 Apr, 2017 1 commit
    • Philipp Tomsich's avatar
      defconfig: puma-rk3399: add defconfig for the RK3399-Q7 (Puma) · 0b3ce83d
      Philipp Tomsich authored and Simon Glass's avatar Simon Glass committed
      
      
      This commit adds the baseline defconfig for the RK3399-Q7 (Puma) SoM
      (under the name 'puma-rk3399_defconfig') featuring the Rockchip RK3399
      in a Qseven compatible module.
      
      This subsumes the following changes:
       * defconfig: rk3399: migrate CONFIG_SPL_LIBCOMMON_SUPPORT/CONFIG_SPL_LIBGENERIC_SUPPORT
       * defconfig: rk3399-puma: add CONFIG_MMC_DW_ROCKCHIP
       * defconfig: rk3399-puma: disable CONFIG_SPL_OF_PLATDATA
       * defconfig: rk3399-puma: don't USE_TINY_PRINTF
       * defconfig: rk3399-puma: set up CONFIG_SYS_BOARD for the RK3399-Q7
       * defconfig: rk3399-puma: enable the multi-image loading via CONFIG_SPL_FIT
       * defconfig: rk3399-puma: SPL should be able to boot from MMC/SD card
       * defconfig: rk3399-puma: enable GMAC support
       * defconfig: rk3399-puma: enable support for SPI and Winbond SPI flash
       * defconfig: rk3399-puma: enable SPI as a boot-source in SPL
       * defconfig: rk3399-puma: disallow non-FIT images from being loaded
       * defconfig: rk3399-puma: rename to puma-rk3399
       * rockchip: config: rk3399: update defconfigs and rk3399_common
      
      For the RK3399-Q7, we want a default boot-order of SPI -> MMC -> uSD.
      This both follows how the BootROM probes devices and is a sane default
      for customers in device-personalisation (e.g. it allows for quick and
      easy factory programming of unpersonalised devices using an SD card)
      and field usage (with customer devices expected to have their firmware
      either in SPI or MMC).
      
      However, when probing multiple interfaces (according to the result
      from the board_boot_order function), we need to ensure that only valid
      FIT images are considered and disable the fallback to assuming that a
      raw (binary-only) U-Boot image is loaded (to avoid hangs/crashes from
      jumping to random content loaded from devices that are probed, but
      don't contain valid image content).
      
      By disabling the SPL_RAW_IMAGE_SUPPORT and SPL_LEGACY_IMAGE_SUPPORT
      options, we ensure that raw images (indistinguishable from random
      data) are not considered for booting.
      Signed-off-by: Philipp Tomsich's avatarPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
      Acked-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      Drop CONFIG_DEBUG_UART_BOARD_INIT:
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      0b3ce83d
  17. 19 Mar, 2017 1 commit
  18. 16 Mar, 2017 1 commit
  19. 13 Mar, 2017 1 commit
  20. 31 Jan, 2017 1 commit
  21. 28 Jan, 2017 3 commits
  22. 12 Jan, 2017 1 commit
    • Simon Glass's avatar
      rockchip: evb-rk3339: Enable DHCP · cea951e0
      Simon Glass authored
      
      
      This is the only RK3399 device without DHCP. Enable it so that we
      can use a common BOOT_TARGET_DEVICES setting. It is likely useful to be
      able to use USB networking, at least. Full networking can be enabled when
      a suitable platform needs it.
      Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      cea951e0
  23. 11 Jan, 2017 2 commits
  24. 29 Dec, 2016 2 commits
  25. 26 Nov, 2016 1 commit
  26. 23 Oct, 2016 1 commit
  27. 12 Oct, 2016 1 commit
  28. 02 Oct, 2016 1 commit
  29. 22 Sep, 2016 3 commits
  30. 09 Sep, 2016 1 commit