1. 23 Jun, 2021 2 commits
  2. 06 Apr, 2021 1 commit
  3. 13 Jan, 2021 2 commits
  4. 12 Jan, 2021 1 commit
  5. 18 Dec, 2020 1 commit
  6. 30 Nov, 2020 1 commit
  7. 12 Nov, 2020 2 commits
  8. 07 Oct, 2020 1 commit
  9. 03 Oct, 2020 1 commit
  10. 25 Sep, 2020 1 commit
  11. 14 Sep, 2020 1 commit
  12. 10 Sep, 2020 1 commit
  13. 18 Aug, 2020 1 commit
  14. 03 Aug, 2020 1 commit
  15. 28 Jul, 2020 1 commit
    • johpow01's avatar
      Fix broken link in documentation · 526f2bdd
      johpow01 authored
      
      
      The link to the exception handling framework page on the System Design /
      Firmware Design / Section 4.3 just links to itself, so I changed it to
      link to the exception handling framework component document.
      Signed-off-by: default avatarJohn Powell <john.powell@arm.com>
      Change-Id: I6711b423a789b2b3d1921671e8497fffa8ba33d1
      526f2bdd
  16. 23 Jul, 2020 1 commit
  17. 30 Jun, 2020 1 commit
  18. 25 Jun, 2020 3 commits
  19. 22 Jun, 2020 2 commits
  20. 01 Jun, 2020 1 commit
  21. 19 May, 2020 1 commit
  22. 17 Apr, 2020 1 commit
  23. 16 Apr, 2020 1 commit
  24. 12 Mar, 2020 3 commits
    • Sandrine Bailleux's avatar
      Mention COT build option in trusted-board-boot-build.rst · d935b951
      Sandrine Bailleux authored
      Since commit 3bff910d
      
       ("Introduce COT
      build option"), it is now possible to select a different Chain of Trust
      than the TBBR-Client one.
      
      Make a few adjustments in the documentation to reflect that. Also make
      some minor improvements (fixing typos, better formatting, ...)  along
      the way.
      
      Change-Id: I3bbadc441557e1e13311b6fd053fdab6b10b1ba2
      Signed-off-by: default avatarSandrine Bailleux <sandrine.bailleux@arm.com>
      d935b951
    • Sandrine Bailleux's avatar
      Update cryptographic algorithms in TBBR doc · 316c5cc6
      Sandrine Bailleux authored
      
      
      The TBBR documentation has been written along with an early
      implementation of the code. At that time, the range of supported
      encryption and hash algorithms was failry limited. Since then, support
      for other algorithms has been added in TF-A but the documentation has
      not been updated.
      
      Instead of listing them all, which would clutter this document while
      still leaving it at risk of going stale in the future, remove specific
      references to the original algorithms and point the reader at the
      relevant comprehensive document for further details.
      
      Change-Id: I29dc50bc1d53b728091a1fbaa1c3970fb999f7d5
      Signed-off-by: default avatarSandrine Bailleux <sandrine.bailleux@arm.com>
      316c5cc6
    • Chris Kay's avatar
      juno/sgm: Maximize space allocated to SCP_BL2 · ddc93cba
      Chris Kay authored
      
      
      To accommodate the increasing size of the SCP_BL2 binary, the base
      address of the memory region allocated to SCP_BL2 has been moved
      downwards from its current (mostly) arbitrary address to the beginning
      of the non-shared trusted SRAM.
      
      Change-Id: I086a3765bf3ea88f45525223d765dc0dbad6b434
      Signed-off-by: default avatarChris Kay <chris.kay@arm.com>
      ddc93cba
  25. 09 Mar, 2020 1 commit
  26. 06 Mar, 2020 1 commit
  27. 02 Mar, 2020 1 commit
  28. 20 Feb, 2020 1 commit
    • Varun Wadekar's avatar
      cpus: higher performance non-cacheable load forwarding · cd0ea184
      Varun Wadekar authored
      
      
      The CPUACTLR_EL1 register on Cortex-A57 CPUs supports a bit to enable
      non-cacheable streaming enhancement. Platforms can set this bit only
      if their memory system meets the requirement that cache line fill
      requests from the Cortex-A57 processor are atomic.
      
      This patch adds support to enable higher performance non-cacheable load
      forwarding for such platforms. Platforms must enable this support by
      setting the 'A57_ENABLE_NONCACHEABLE_LOAD_FWD' flag from their
      makefiles. This flag is disabled by default.
      
      Change-Id: Ib27e55dd68d11a50962c0bbc5b89072208b4bac5
      Signed-off-by: default avatarVarun Wadekar <vwadekar@nvidia.com>
      cd0ea184
  29. 12 Feb, 2020 1 commit
  30. 06 Feb, 2020 1 commit
    • Max Shvetsov's avatar
      Adds option to read ROTPK from registers for FVP · a6ffddec
      Max Shvetsov authored
      
      
      Enables usage of ARM_ROTPK_LOCATION=regs for FVP board.
      Removes hard-coded developer keys. Instead, setting
      ARM_ROTPK_LOCATION=devel_* takes keys from default directory.
      In case of ROT_KEY specified - generates a new hash and replaces the
      original.
      
      Note: Juno board was tested by original feature author and was not tested
      for this patch since we don't have access to the private key. Juno
      implementation was moved to board-specific file without changing
      functionality. It is not known whether byte-swapping is still needed
      for this platform.
      
      Change-Id: I0fdbaca0415cdcd78f3a388551c2e478c01ed986
      Signed-off-by: default avatarMax Shvetsov <maksims.svecovs@arm.com>
      a6ffddec
  31. 27 Jan, 2020 1 commit
  32. 29 Dec, 2019 1 commit
    • Samuel Holland's avatar
      bl31: Split into two separate memory regions · f8578e64
      Samuel Holland authored
      
      
      Some platforms are extremely memory constrained and must split BL31
      between multiple non-contiguous areas in SRAM. Allow the NOBITS
      sections (.bss, stacks, page tables, and coherent memory) to be placed
      in a separate region of RAM from the loaded firmware image.
      
      Because the NOBITS region may be at a lower address than the rest of
      BL31, __RW_{START,END}__ and __BL31_{START,END}__ cannot include this
      region, or el3_entrypoint_common would attempt to invalidate the dcache
      for the entire address space. New symbols __NOBITS_{START,END}__ are
      added when SEPARATE_NOBITS_REGION is enabled, and the dcached for the
      NOBITS region is invalidated separately.
      Signed-off-by: default avatarSamuel Holland <samuel@sholland.org>
      Change-Id: Idedfec5e4dbee77e94f2fdd356e6ae6f4dc79d37
      f8578e64