Skip to content
Snippets Groups Projects
  1. Aug 13, 2019
  2. Apr 25, 2019
  3. Nov 26, 2018
  4. Nov 05, 2018
  5. Oct 26, 2018
  6. May 29, 2018
  7. May 23, 2018
  8. Apr 17, 2018
  9. Mar 02, 2018
    • Joel Anderson's avatar
      qemu_v8.mk: update strace-clean to test for Makefile · b60156e8
      Joel Anderson authored
      
      The 'strace-clean' target runs the 'clean' target in the strace project
      directly, and afterwards removes the Makefile and configure scripts as well.
      This is the same strategy used by other platforms using strace (hikey.mk and
      hikey960.mk), however other platforms check for the existence of the Makefile
      before executing $(MAKE), allowing a build to be cleaned multiple times.
      Without this check, subsequent invocations of 'strace-clean' (or simply
      'clean') fail as there is no Makefile to use.
      
      Fixes:
      
      $ make strace-clean
      [...]
      $ make strace-clean
      [...]
      make[1]: Entering directory '/home/goatshriek/optee-armv8/strace'
      make[1]: *** No rule to make target 'clean'.  Stop.
      
      Signed-off-by: default avatarJoel Anderson <jeander@vt.edu>
      Reviewed-by: default avatarJerome Forissier <jerome.forissier@linaro.org>
      b60156e8
  10. Feb 26, 2018
    • Jerome Forissier's avatar
      qemu_v8.mk: update edk2-call to invoke the EDK2 build script · 571e2daf
      Jerome Forissier authored
      
      Like other platforms (fvp.mk, hikey.mk, hikey960.mk, hikey_debian.mk)
      define the edk2-call macro to invoke the EDK2 build script rather than
      $(MAKE) directly. Indeed, the edk2-clean-common target in common.mk
      expects $(edk2-call) to take the 'cleanall' argument, which the EDK2
      build script does accept, but the EDK2 makefile doesn't (there is no
      cleanall rule in EDK2).
      
      Fixes:
      
       $ make clean
       [...]
       make[1]: Entering directory '/home/jerome/optee_repo_qemu_v8/edk2'
       make[1]: *** No rule to make target 'cleanall'.  Stop.
      
      Another option to fix the above error would be to change the edk2-clean
      target to no use edk2-clean-common and call "$(MAKE) clean" directly.
      But then, it would be inconsistent with other platforms and the EDK2
      build script may be a better interface than raw make (more stable).
      
      Signed-off-by: default avatarJerome Forissier <jerome.forissier@linaro.org>
      Reported-by: default avatarJoel Anderson <jeander@vt.edu>
      Acked-by: default avatarJens Wiklander <jens.wiklander@linaro.org>
      571e2daf
  11. Jan 16, 2018
  12. Nov 27, 2017
    • Joakim Bech's avatar
      edk2: Update QEMU v8 and FVP builds · c94e95a7
      Joakim Bech authored
      
      QEMU v8 and FVP are both now working with upstream edk2 and
      edk2-platforms. QEMU v8's dsc file is located in the edk2 folder whilst
      the dsc for FVP is in the edk2-platforms folder. Due to this we had to
      export the WORKSPACE variable differently otherwise we would get either
      compiler errors or we would get the "Build" folder created on the top
      level (something that we do not want).
      
      Signed-off-by: default avatarJoakim Bech <joakim.bech@linaro.org>
      Tested-by: Joakim Bech <joakim.bech@linaro.org> (QEMU v8, FVP)
      Reviewed-by: default avatarJerome Forissier <jerome.forissier@linaro.org>
      c94e95a7
  13. Oct 30, 2017
  14. Oct 29, 2017
  15. Oct 23, 2017
    • Jerome Forissier's avatar
      qemu_v8.mk: remove ARM-TF flag: ERROR_DEPRECATED=1 · 908c823e
      Jerome Forissier authored
      
      ERROR_DEPRECATED=1 may cause build errors when ARM deprecates APIs
      upstream. Since we're tracking upstream master, it can happen at any
      time, and indeed we have just met this build issue:
      
       plat/qemu/qemu_bl31_setup.c:129:2: error: unknown field 'g0_interrupt_num' specified in initializer
         .g0_interrupt_num = ARRAY_SIZE(irq_sec_array),
         ^
      
      Although we usually want to use the latest APIs, having a build that
      can break randomly is not nice to our users. Therefore, remove the
      ERROR_DEPRECATED flag from our Makefile to fix the compile error and
      give us some time to adapt to upstream changes.
      
      Of course, the weakness in this reasoning is that by removing
      ERROR_DEPRECATED, we are likely to not even notice when an API has
      changed. Anyway, this seems to be the most reasonable option given that
      there is no WARN_DEPRECATED flag.
      
      Signed-off-by: default avatarJerome Forissier <jerome.forissier@linaro.org>
      Reviewed-by: default avatarJoakim Bech <joakim.bech@linaro.org>
      2.6.0
      908c823e
  16. Oct 09, 2017
  17. Sep 07, 2017
  18. Sep 04, 2017
  19. Jul 25, 2017
  20. May 24, 2017
  21. Apr 06, 2017
  22. Apr 05, 2017
  23. Mar 11, 2017
  24. Feb 02, 2017
  25. Jan 31, 2017
  26. Oct 26, 2016
  27. Oct 21, 2016
  28. Oct 06, 2016
  29. Jul 19, 2016
  30. Jul 11, 2016
  31. May 25, 2016
    • Joakim Bech's avatar
      gcc5: Update to use gcc5 · 69a8a37b
      Joakim Bech authored
      
      - Adds legacy toolchain for use in older edk2 projects, this is the only
        project using the pre 5.x toolchain for now
      - Removes the bare metal toolchain
      - qemu: Change the path for libraries for GCC5
      - fvp: compiler changes for ARM-TF and EDK2
             Update libteec path in initramfs
      - mtk: Toolchain and libteec path updates
      - juno: Toolchain and libteec path updates
      
      Signed-off-by: default avatarJoakim Bech <joakim.bech@linaro.org>
      Tested-by: Joakim Bech <joakim.bech@linaro.org> (QEMU, FVP, HiKey)
      Tested-by: Pascal Brand <pascal.brand@linaro.org> (QEMU)
      Tested-by: Pascal Brand <pascal.brand@linaro.org> (FVP)
      69a8a37b
  32. Apr 27, 2016
  33. Apr 25, 2016
  34. Mar 22, 2016
Loading