1. 18 10月, 2020 1 次提交
  2. 24 8月, 2020 1 次提交
  3. 08 8月, 2020 1 次提交
  4. 19 5月, 2020 1 次提交
  5. 09 5月, 2020 1 次提交
  6. 15 1月, 2020 1 次提交
  7. 21 11月, 2019 1 次提交
    • 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
  8. 14 10月, 2019 1 次提交
  9. 08 10月, 2019 4 次提交
  10. 27 6月, 2019 1 次提交
  11. 11 6月, 2019 1 次提交
  12. 05 5月, 2019 1 次提交
  13. 26 4月, 2019 1 次提交
  14. 28 1月, 2019 1 次提交
  15. 01 1月, 2019 1 次提交
    • F
      pico-imx7d: Increase the CONFIG_ENV_OFFSET size · 57d2beb9
      Fabio Estevam 提交于
      U-Boot binary has grown in such a way that it goes beyond the reserved
      area for the environment variables.
      
      Running "saveenv" causes U-Boot to hang because of this overlap.
      
      Fix this problem by increasing the CONFIG_ENV_OFFSET size.
      
      Also, in order to prevent this same problem in the future, use
      CONFIG_BOARD_SIZE_LIMIT, which will detect the overlap in build-time.
      
      CONFIG_BOARD_SIZE_LIMIT does not accept math expressions, so declare
      CONFIG_ENV_OFFSET with its direct value instead.
      Signed-off-by: NFabio Estevam <festevam@gmail.com>
      Acked-by: NOtavio Salvador <otavio@ossystems.com.br>
      57d2beb9
  16. 10 10月, 2018 2 次提交
  17. 18 9月, 2018 1 次提交
  18. 18 8月, 2018 1 次提交
  19. 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
  20. 23 7月, 2018 10 次提交
  21. 18 6月, 2018 1 次提交
  22. 07 5月, 2018 1 次提交
    • T
      SPDX: Convert all of our single license tags to Linux Kernel style · 83d290c5
      Tom Rini 提交于
      When U-Boot started using SPDX tags we were among the early adopters and
      there weren't a lot of other examples to borrow from.  So we picked the
      area of the file that usually had a full license text and replaced it
      with an appropriate SPDX-License-Identifier: entry.  Since then, the
      Linux Kernel has adopted SPDX tags and they place it as the very first
      line in a file (except where shebangs are used, then it's second line)
      and with slightly different comment styles than us.
      
      In part due to community overlap, in part due to better tag visibility
      and in part for other minor reasons, switch over to that style.
      
      This commit changes all instances where we have a single declared
      license in the tag as both the before and after are identical in tag
      contents.  There's also a few places where I found we did not have a tag
      and have introduced one.
      Signed-off-by: NTom Rini <trini@konsulko.com>
      83d290c5
  23. 15 4月, 2018 1 次提交
  24. 02 2月, 2018 1 次提交
  25. 08 8月, 2017 1 次提交
  26. 26 7月, 2017 1 次提交
    • S
      Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig · 2be29653
      Simon Glass 提交于
      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: NSimon Glass <sjg@chromium.org>
      Signed-off-by: NTom Rini <trini@konsulko.com>
      2be29653
  27. 31 5月, 2017 1 次提交