Skip to content
Snippets Groups Projects
  1. Aug 13, 2019
  2. Aug 07, 2019
  3. Jun 28, 2019
  4. Jun 11, 2019
  5. Jun 03, 2019
  6. May 23, 2019
    • Joakim Bech's avatar
      buildroot: Update toolchain and kernel headers · 6e167bf1
      Joakim Bech authored
      
      The BR2_KERNEL_HEADERS_4_10 has been depracted, so when trying to build
      with GDBSERVER=y we got this warning:
      
        Makefile.legacy:9: *** "You have legacy configuration in your .config!
        Please check your configuration.".  Stop.
      
      To better match recent toolchain updates in this git (gcc updates and
      kernel header updates, commit e0298161), we also update buildroot to
      use and provide a GCC8.x based toolchain as well as 4.19 kernel headers.
      
      Signed-off-by: default avatarJoakim Bech <joakim.bech@linaro.org>
      Tested-by: Joakim Bech <joakim.bech@linaro.org> (QEMU v7)
      Acked-by: default avatarJerome Forissier <jerome@forissier.org>
      6e167bf1
  7. May 18, 2019
    • Joakim Bech's avatar
      toolchain: Update to GCC 8.3 and update kernel headers · e0298161
      Joakim Bech authored
      
      In the GCC v8.2-2018.08 toolchain (previous default in OP-TEE) the
      GDB/TUI mode was disabled, which made debugging using GDB slightly more
      complicated. However, in more recent versions of GCC like the one
      introduced here, i.e., GCC8.3-2019.03, Arm have re-enabled the TUI mode.
      
      But to be able to upgrade the toolchain, one must also step up kernel
      headers so that the toolchain matches the kernel headers used by
      Buildroot. This means that we are stepping up from 4.18 kernel headers
      to 4.19 kernel headers, which seems to be compatible with the version of
      GCC that is being introduced in this patch.
      
      Note that after this commit, older GCC versions will not work any
      longer when building full OP-TEE developer setups using OP-TEE's
      manifest.git and build.git, i.e., trying to run GCC8.2 for example will
      give a kernel header mismatch error.
      
      Fixes #334.
      
      Signed-off-by: default avatarJoakim Bech <joakim.bech@linaro.org>
      Tested-by: Joakim Bech <joakim.bech@linaro.org> (QEMU v7, v8)
      Acked-by: default avatarJerome Forissier <jerome.forissier@linaro.org>
      e0298161
  8. May 13, 2019
  9. May 10, 2019
  10. May 06, 2019
  11. May 02, 2019
  12. Apr 30, 2019
  13. Apr 25, 2019
  14. Apr 24, 2019
  15. Mar 19, 2019
  16. Mar 06, 2019
  17. Feb 22, 2019
  18. Feb 06, 2019
  19. Feb 04, 2019
  20. Feb 01, 2019
  21. Jan 29, 2019
  22. Jan 16, 2019
    • Joakim Bech's avatar
      rpi3: Set RPI3_PRELOADED_DTB_BASE for TF-A · bbfcc268
      Joakim Bech authored
      
      In TF-A in the commit:
         (5341b42ec) rpi3: Add mem reserve region to DTB if present
      
      they started to runtime patching of the DTB, but the default build rules
      in TF-A doesn't set RPI3_PRELOADED_DTB_BASE to anything which then gets
      set to the default value: 1, which gives incorrect memory mappings for
      MAP_BL32_MEM. Therefore we must tell where the DTB is located and we do
      that by adding adding a compile time flag to TF-A, i.e.,
      
             RPI3_PRELOADED_DTB_BASE=0x00010000
      
      Signed-off-by: default avatarJoakim Bech <joakim.bech@linaro.org>
      Tested-by: Joakim Bech <joakim.bech@linaro.org> (RPi3)
      Reviewed-by: default avatarIgor Opaniuk <igor.opaniuk@linaro.org>
      3.4.0
      bbfcc268
  23. Jan 14, 2019
  24. Dec 21, 2018
  25. Nov 26, 2018
  26. Nov 12, 2018
  27. Nov 09, 2018
Loading