1. 18 10月, 2020 1 次提交
  2. 10 10月, 2020 1 次提交
  3. 24 8月, 2020 1 次提交
  4. 29 7月, 2020 1 次提交
  5. 28 7月, 2020 1 次提交
  6. 17 7月, 2020 1 次提交
  7. 07 7月, 2020 1 次提交
  8. 09 5月, 2020 1 次提交
  9. 07 2月, 2020 1 次提交
  10. 23 1月, 2020 1 次提交
  11. 15 1月, 2020 2 次提交
  12. 06 12月, 2019 1 次提交
  13. 04 12月, 2019 1 次提交
  14. 21 11月, 2019 2 次提交
    • T
      env: Finish migration of common ENV options · a09fea1d
      Tom Rini 提交于
      - 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 <wd@denx.de>
      Cc: Joe Hershberger <joe.hershberger@ni.com>
      Cc: Patrick Delaunay <patrick.delaunay@st.com>
      Cc: uboot-stm32@st-md-mailman.stormreply.com
      Signed-off-by: NTom Rini <trini@konsulko.com>
      Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
      Reviewed-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
      a09fea1d
    • T
      env: Add CONFIG_SYS_RELOC_GD_ENV_ADDR symbol · 8d8ee47e
      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 <wd@denx.de>
      Cc: Joe Hershberger <joe.hershberger@ni.com>
      Signed-off-by: NTom Rini <trini@konsulko.com>
      8d8ee47e
  15. 08 11月, 2019 1 次提交
  16. 14 10月, 2019 1 次提交
  17. 08 10月, 2019 2 次提交
  18. 24 8月, 2019 1 次提交
  19. 14 8月, 2019 1 次提交
  20. 20 7月, 2019 1 次提交
  21. 23 6月, 2019 1 次提交
  22. 11 6月, 2019 1 次提交
  23. 27 5月, 2019 1 次提交
  24. 05 5月, 2019 1 次提交
  25. 30 4月, 2019 2 次提交
  26. 26 4月, 2019 3 次提交
  27. 28 1月, 2019 1 次提交
  28. 19 1月, 2019 1 次提交
    • P
      Kconfig: Migrate BOUNCE_BUFFER · 2acc24fc
      Philipp Tomsich 提交于
      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: NTom Rini <trini@konsulko.com>
      Signed-off-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
      Reviewed-by: Otavio Salvador <otavio@ossystems.com.br> [dw_mmc portion]
      Reviewed-by: Fabio Estevam <festevam@gmail.com> [mxsmmc portion]
      Reviewed-by: Simon Glass <sjg@chromium.org> [tegra portion]
      2acc24fc
  29. 11 1月, 2019 1 次提交
  30. 08 1月, 2019 1 次提交
  31. 10 10月, 2018 1 次提交
  32. 18 8月, 2018 1 次提交
  33. 17 8月, 2018 1 次提交
    • T
      configs: Migrate CONFIG_NR_DRAM_BANKS · 86cf1c82
      Tom Rini 提交于
      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: NTom Rini <trini@konsulko.com>
      86cf1c82
  34. 23 7月, 2018 1 次提交