1
0
Fork 0

Adding permissions into apex
Some checks failed
macOS-CI / macOS-CI (dri) (push) Has been cancelled
macOS-CI / macOS-CI (xlib) (push) Has been cancelled

This commit is contained in:
dvab-sarma 2025-12-05 13:07:11 -06:00
parent 188402e129
commit 65fa67abf7
3 changed files with 12 additions and 7 deletions

View file

@ -26,11 +26,17 @@ apex {
updatable: false,
vendor: true,
prebuilts: [
"android.hardware.vulkan.panfrost-linker-config",
"android.hardware.vulkan.panfrost.rc",
],
native_shared_libs: [
"vulkan.panfrost",
],
prebuilts: [
"android.hardware.vulkan.panfrost-linker-config",
"android.hardware.vulkan.panfrost.rc",
"android.software.vulkan.deqp.level-latest.prebuilt.xml",
"android.hardware.vulkan.version-1_3.prebuilt.xml",
"android.hardware.vulkan.compute-0.prebuilt.xml",
"android.hardware.vulkan.level-1.prebuilt.xml",
],
}

View file

@ -2,5 +2,5 @@
# But the vulkan apex is okay because it's bootstrap APEX.
# For bootstrap APEXes, `on init` is the earliest available trigger.
on init
setprop ro.hardware.vulkan panfrost
setprop ro.vulkan.apex com.android.hardware.vulkan.panfrost
setprop ro.hardware.vulkan panfrost

View file

@ -1,4 +1,3 @@
{
// visible so that vulkan loader can see
"visible": true
}