Skip to content
Snippets Groups Projects
  1. Jul 25, 2017
  2. Jul 11, 2017
  3. Jun 19, 2017
  4. Jun 07, 2017
  5. May 10, 2017
  6. May 01, 2017
  7. Apr 27, 2017
  8. Apr 15, 2017
  9. Apr 05, 2017
    • Philipp Tomsich's avatar
      defconfig: puma-rk3399: add defconfig for the RK3399-Q7 (Puma) · 0b3ce83d
      Philipp Tomsich authored
      
      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: default avatarPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      Drop CONFIG_DEBUG_UART_BOARD_INIT:
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      0b3ce83d
  10. Mar 19, 2017
  11. Mar 16, 2017
  12. Mar 13, 2017
  13. Jan 31, 2017
  14. Jan 28, 2017
  15. Jan 12, 2017
    • 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: default avatarSimon Glass <sjg@chromium.org>
      cea951e0
  16. Jan 11, 2017
  17. Dec 29, 2016
  18. Nov 26, 2016
  19. Oct 23, 2016
  20. Oct 12, 2016
  21. Oct 02, 2016
  22. Sep 22, 2016
  23. Sep 09, 2016
  24. Aug 06, 2016
  25. Jul 26, 2016
Loading