1. 19 6月, 2020 1 次提交
  2. 22 4月, 2020 1 次提交
    • M
      ARM: rmobile: Increase malloc area size · 80a624f2
      Marek Vasut 提交于
      Increase the malloc area size significantly to cater for bounce buffer
      used by the SDHI driver.
      Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com>
      Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
      Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
      Cc: Peng Fan <peng.fan@nxp.com>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Tom Rini <trini@konsulko.com>
      80a624f2
  3. 02 3月, 2020 1 次提交
  4. 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: Remove useless CONFIG_ENV_SIZE_REDUND and fix ENV_IS_REDUND check · a8992e78
      Tom Rini 提交于
      We have CONFIG_ENV_SIZE_IS_REDUND but don't really use it.  We have one
      board where we can simply multiple CONFIG_ENV_SIZE by two for the same
      result.  The other place where we could but were not previously using
      this is for where env_internal.h checks for if we should set
      ENV_IS_EMBEDDED.  This seems like the most likely use, historically, of
      the variable, but it was not used.  Add logic to check for this now.
      
      Cc: Wolfgang Denk <wd@denx.de>
      Cc: Joe Hershberger <joe.hershberger@ni.com>
      Signed-off-by: NTom Rini <trini@konsulko.com>
      Reviewed-by: NSimon Glass <sjg@chromium.org>
      Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
      a8992e78
  5. 26 8月, 2019 1 次提交
  6. 02 8月, 2019 1 次提交
  7. 22 5月, 2019 1 次提交
    • M
      ARM: rmobile: Add recovery SPL for R-Car Gen3 · 5602330d
      Marek Vasut 提交于
      Build an SPL which can be started via SCIF download mode on R-Car Gen3
      and allows loading and executing U-Boot uImage with the next stage code.
      This is also useful for starting e.g. ATF BL2, which inits the hardware
      and returns to the U-Boot SPL, which can then load e.g. U-Boot proper.
      
      The H3, M3-W, M3-N SoCs have plenty of SRAM for storing the U-Boot SPL
      while the payload, e.g. ATF BL2, executes, so there is no problem here.
      
      However, E3 and D3 have much less SRAM, hence the loader uses a trick
      where it copies itself beyond the area used by BL2 and executes from
      there. That area is 32kiB large and not enough to hold U-Boot SPL, BSS,
      stack and malloc area, so the later two are placed at +0x4000 offset
      from start of SRAM, another area not used by ATF BL2. To make things
      even more complicated, the SCIF loader cannot load to the upper 32kiB
      of the SRAM directly, hence the copying approach.
      Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com>
      Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
      5602330d
  8. 10 3月, 2019 1 次提交
    • E
      ARM: rmobile: rcar-gen3: Activate bootm_size · d245059f
      Eugeniu Rosca 提交于
      v2019.01 commit 07a8060a ("ARM: rmobile: Convert to bootm_size")
      attempted converting to bootm_size of 256 MiB below targets:
       - include/configs/alt.h
       - include/configs/gose.h
       - include/configs/koelsch.h
       - include/configs/lager.h
       - include/configs/porter.h
       - include/configs/rcar-gen3-common.h
       - include/configs/silk.h
       - include/configs/stout.h
      
      The update didn't fully work on R-Car3 due to the
      CONFIG_SYS_BOOTMAPSZ=8MiB definition left by v2016.09 commit
      e525d34b ("ARM: rmobile: Add support salvator-x board"),
      which is explained in below README excerpt:
      
      ----8<----
      CONFIG_SYS_BOOTMAPSZ:
                      [..] If CONFIG_SYS_BOOTMAPSZ is undefined,
                      then the value in "bootm_size" will be used instead.
      ----8<----
      
      Allow the original commit to accomplish its purpose on R-Car3 targets
      by removing the CONFIG_SYS_BOOTMAPSZ definition.
      
      Fixes: 07a8060a ("ARM: rmobile: Convert to bootm_size")
      Signed-off-by: NEugeniu Rosca <erosca@de.adit-jv.com>
      d245059f
  9. 02 2月, 2019 1 次提交
  10. 04 12月, 2018 1 次提交
    • M
      ARM: rmobile: Convert to bootm_size · 07a8060a
      Marek Vasut 提交于
      Convert all Renesas R-Car boards to bootm_size of 256 MiB and drop both
      fdt_high and initrd_high. This change implies that the FDT and initrd
      will always be copied into the first 256 MiB of RAM instead of being
      used in place, which can cause various kinds of inobvious problems.
      
      The simpler problems include FDT or initrd being overwritten or being
      used from unaligned addresses, especially on ARM64. The overhead of
      copying the FDT to aligned location is negligible and these problems
      go away, so the benefit is significant.
      
      Regarding alignment problems with fitImage. The alignment of DT properties
      is always 32 bits, which implies that the alignment of the "data" property
      in fitImage is also 32 bits. The /incbin/ syntax plays no role here. The
      kernel expects all elements, including DT and initrd, to be aligned to
      64 bits on ARM64, thus using them in place may not be possible. Using the
      bootm_size assures correct alignment, again with negligible overhead.
      Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com>
      Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
      Cc: Tom Rini <trini@konsulko.com>
      07a8060a
  11. 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
  12. 15 6月, 2018 1 次提交
    • M
      ARM: rmobile: Point load address to more sane area on Gen3 · 4b334b60
      Marek Vasut 提交于
      Point the $loadaddr variable and default load address to a more sane
      area, 384 MiB from the start of RAM. This is to avoid all the reserved
      memory at the beginning of RAM. The old behavior could still be easily
      retained by "setenv loadaddr 0x48080000" . The new setup allows us to
      use for example modern fitImage with kernel_noload, so use this as a
      new preferred default.
      Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com>
      Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
      4b334b60
  13. 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
  14. 12 4月, 2018 1 次提交
  15. 28 2月, 2018 1 次提交
  16. 24 2月, 2018 1 次提交
  17. 16 2月, 2018 1 次提交
  18. 11 2月, 2018 1 次提交
    • T
      configs: Migrate CONFIG_SYS_TEXT_BASE · 278b90ce
      Tom Rini 提交于
      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: NTom Rini <trini@konsulko.com>
      278b90ce
  19. 23 1月, 2018 2 次提交
  20. 09 12月, 2017 1 次提交
  21. 30 11月, 2017 2 次提交
  22. 28 9月, 2017 1 次提交
  23. 24 9月, 2017 2 次提交
  24. 04 9月, 2017 1 次提交
  25. 15 8月, 2017 1 次提交
  26. 12 8月, 2017 1 次提交
  27. 03 8月, 2017 1 次提交
  28. 04 6月, 2017 1 次提交
  29. 22 5月, 2017 4 次提交
  30. 01 5月, 2017 1 次提交
  31. 20 3月, 2017 1 次提交
  32. 28 1月, 2017 1 次提交
  33. 26 1月, 2017 1 次提交