Venkat Yadlapati wrote: > Which listener or QTEE state does PIL init depend on for these > subsystems, and is there a way to provide it from mainline?
Hi Sumit, Rob, Please disregard my question, it was my mistake: the zap shader I loaded was signed with the wrong key. The stock vendor partition carries two copies of the GPU firmware. /vendor/firmware/gen80900_zap.mbn is signed with the Qualcomm "SECTOOLS SECP384R1 CURVE TEST ROOT". Android loads the copy from the modem partition (/vendor/firmware_mnt/image/gen80900_zap.mbn), which is signed by the OEM. I had packaged the first one, and the production TZ rejects it with 0x300045. The early Android failure I described was the same thing: the video driver probed before the modem partition was mounted and picked up the test-signed /vendor/firmware/vpu40_1v.mbn. The later successes after qseecomd started were a coincidence, PAS loads keep working on Android with qseecomd and keymint stopped. With the OEM-signed zap, PAS init for 13 succeeds on mainline without any QTEE listener. Sorry for the noise, and thanks for looking. Venkat
