rpi3: change firmware remote revision back to tag

SHA-1 hashes can't be used mutually with clone-depth="1".
Although since Git version 2.5 servers may expose raw hashes,
it's common practice to disable this feature (it's
server-side configuration item) because of security flaws.

Fixes: https://github.com/OP-TEE/manifest/issues/88

Acked-by: Jerome Forissier <jerome.forissier@linaro.org>
Tested-by: Jerome Forissier <jerome.forissier@linaro.org>
Signed-off-by: Igor Opaniuk <igor.opaniuk@linaro.org>
1 file changed
tree: bcf39950015dff42777683d930a369ac3f96c033
  1. .travis.yml
  2. am43xx.xml
  3. am43xx_stable.xml
  4. am57xx.xml
  5. am57xx_stable.xml
  6. default.xml
  7. default_stable.xml
  8. dra7xx.xml
  9. dra7xx_stable.xml
  10. fvp.xml
  11. fvp_stable.xml
  12. hikey.xml
  13. hikey960.xml
  14. hikey960_stable.xml
  15. hikey_debian.xml
  16. hikey_debian_stable.xml
  17. hikey_stable.xml
  18. juno.xml
  19. juno_stable.xml
  20. mt8173-evb.xml
  21. mt8173-evb_stable.xml
  22. qemu_v8.xml
  23. qemu_v8_stable.xml
  24. README.md
  25. rpi3.xml
  26. rpi3_stable.xml
  27. travis.xml
README.md

Repo manifest for OP-TEE development

In the OP-TEE project we try to gather all documentation under the optee_os git, therefore we recommend that you read the instructions at this page which describes how to setup OP-TEE on various platforms.