g12: Guard prebuilt tee*/keymaster for devices with no OP-TEE
authorJan Altensen <info@stricted.net>
Fri, 2 Jul 2021 05:43:16 +0000 (07:43 +0200)
committerNolen Johnson <johnsonnolen@gmail.com>
Tue, 27 Jul 2021 21:19:04 +0000 (17:19 -0400)
commita4badd77fb8f948a86e94da05c43d24da8cb36df
treebde126338760b211bb2a558ce3af9d37c6eca137
parentf1e8b823975e659cb01df321f1d78bd9ffbeba86
g12: Guard prebuilt tee*/keymaster for devices with no OP-TEE

* These need to be split out because development
  boards don't have OP-TEE, and even if they could
  kang another device's, we have no functional keys
  or TA files, so it's useless and broken.

* Devices that have no OP-TEE need to set
  `TARGET_HAS_TEE := false` in their lineage_${DEVICE}.mk.

* So that we can successfully encrypt as per the fstab
  entry for `/data`,  build the AOSP keymaster 4.1 service,
  and that uses a VINTF fragment.

Change-Id: I8756ba2d9cd5c53725645185783f9e15b739602c
BoardConfigCommon.mk
extract-files.sh
g12.mk
manifest-tee.xml [new file with mode: 0644]
manifest.xml
proprietary-files-tee.txt [new file with mode: 0644]
proprietary-files.txt
setup-makefiles.sh