halcyonlv/vendor_xiaomi_peridot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

peridot: Import hal uuid map

Browse Source 
Change-Id: I7b2663e116fab40f681dc7b96fd9c41bd445633e
This commit is contained in:
AdarshGrewal
2026-01-29 00:38:29 +05:30
parent 530d7b23d6
commit a6306613da
2 changed files with 0 additions and 69 deletions
Download Patch File Download Diff File Expand all files Collapse all files
peridot-vendor.mk
-1
View File
@@ -910,7 +910,6 @@ PRODUCT_COPY_FILES += \
vendor/xiaomi/peridot/proprietary/vendor/etc/gpfspath_oem_config.xml:$(TARGET_COPY_OUT_VENDOR)/etc/gpfspath_oem_config.xml \
vendor/xiaomi/peridot/proprietary/vendor/etc/gps.conf:$(TARGET_COPY_OUT_VENDOR)/etc/gps.conf \
vendor/xiaomi/peridot/proprietary/vendor/etc/gps_diag.cfg:$(TARGET_COPY_OUT_VENDOR)/etc/gps_diag.cfg \
vendor/xiaomi/peridot/proprietary/vendor/etc/hal_uuid_map_peridot.xml:$(TARGET_COPY_OUT_VENDOR)/etc/hal_uuid_map_peridot.xml \
vendor/xiaomi/peridot/proprietary/vendor/etc/init/android.hardware.bluetooth@1.1-service-qti.rc:$(TARGET_COPY_OUT_VENDOR)/etc/init/android.hardware.bluetooth@1.1-service-qti.rc \
vendor/xiaomi/peridot/proprietary/vendor/etc/init/android.hardware.drm@1.1-service.wfdhdcp.rc:$(TARGET_COPY_OUT_VENDOR)/etc/init/android.hardware.drm@1.1-service.wfdhdcp.rc \
vendor/xiaomi/peridot/proprietary/vendor/etc/init/android.hardware.gatekeeper-service-qti.rc:$(TARGET_COPY_OUT_VENDOR)/etc/init/android.hardware.gatekeeper-service-qti.rc \
proprietary/vendor/etc/hal_uuid_map_peridot.xml
Vendored
-68
View File
@@ -1,68 +0,0 @@
<!-- Copyright (C) 2020 The Android Open Source Project -->
<!-- Copyright 2021 NXP -->
<!-- Licensed under the Apache License, Version 2.0 (the "License"); -->
<!-- you may not use this file except in compliance with the License. -->
<!-- You may obtain a copy of the License at -->
<!-- http://www.apache.org/licenses/LICENSE-2.0 -->
<!-- Unless required by applicable law or agreed to in writing, software -->
<!-- distributed under the License is distributed on an "AS IS" BASIS, -->
<!-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -->
<!-- See the License for the specific language governing permissions and -->
<!-- limitations under the License. -->
<!-- Vendor mapping file -->
<!-- Sample UUID to list of UIDs mapping file -->
<!-- UUID: Universally Unique IDentifier -->
<!-- 16 Byte UUID need to be generated by vendors to add new entry -->
<!-- As per global platform access control spec, UUID is expected to be of -->
<!-- length 20 bytes. While using this UUID, it is expected to be -->
<!-- automatically padded with ffffffff in initial 4 bytes of 20 Byte length -->
<!-- UID: user identifier of the service -->
<!-- This mapping file should contain an entry for VTS tests, since VTS -->
<!-- tests run as root, user identifier 0 should be mapped to its -->
<!-- corresponding UUID to allow VTS tests to access secure element -->
<!-- For VTS tests use UID: 0 and UUID: 9f36407ead0639fc966f14dde7970f68 -->
<ref_do>
<!-- mapping entries to map unique identifiers to device hal services -->
<!-- uids -->
<!-- UUID would be automatically padding with ffffffff to fulfill 20 -->
<!-- bytes in access rule. For example for -->
<!-- UUID:9f36407ead0639fc966f14dde7970f68 after padding it should look -->
<!-- like ffffffff9f36407ead0639fc966f14dde7970f68 -->
<uuid_ref_do>
<uids>
<uid>0</uid>
</uids>
<uuid>9f36407ead0639fc966f14dde7970f68</uuid>
</uuid_ref_do>
<!-- NXP KEYMINT (UID = 2910), WEAVER (UID = 2911) -->
<!-- and AUTHSECRET (UID = 2915) mapping -->
<!-- with UUID = 636F6D2E6E78702E7365637572697479-->
<uuid_ref_do>
<uids>
<uid>2910</uid>
<uid>2911</uid>
<uid>2915</uid>
</uids>
<uuid>636F6D2E6E78702E7365637572697479</uuid>
</uuid_ref_do>
<!-- STM KEYMINT (UID = 2913) and WEAVER (UID = 1087) mapping -->
<!-- with UUID = 534552454144595f48414c5f55554944-->
<uuid_ref_do>
<uids>
<uid>1087</uid>
<uid>2913</uid>
</uids>
<uuid>534552454144595f48414c5f55554944</uuid>
</uuid_ref_do>
</ref_do>