In case of always, we always enable hdcp regardless of drm status.
Bug: 359951297
Flag: EXEMPT bugfix
Change-Id: I04b5174be296d93a9f898929706785d50116d7a7
Signed-off-by: Ji Soo Shin <jisshin@google.com>
For PDK build, the "vendor/arm" path doesn't exist. The modules will be
built from vendor/google_devices/zuma/prebuilts/gpu.
Flag: EXEMPT bugfix
Bug: 357770476
Test: 1. lunch akita-trunk_staging-eng
2. m libGLES_mali vulkan.mali libOpenCL libgpudataproducer
Change-Id: I97631ffdc98b77b747f0abbc7e376d8fbe2a576d
Set the variable is true when USE_LASSEN_OEMHOOK is true and
BOARD_WITHOUT_RADIO is not true.
Flag: EXEMPT bugfix
Bug: 325857852
Test: lunch akita-trunk_staging-userdebug && m ConnectivityMonitor
Change-Id: I44df84ade1c8394a562b523264d5f3f08cb5b5b3
Pixel has removed unnecessary allocation padding, and we now pass
dEQP with a maximum physical core index setting of 4, which allows
the driver to utilize 2 GPU cores (1001b) in the extreme tests.
Bug: 221255664
Test: HK3 atest CtsDeqpTestCases -- --module-arg 'CtsDeqpTestCases:include-filter:dEQP-VK.protected_memory.*'
Flag: EXEMPT bugfix
Change-Id: I96a38a6070968100ce3adf01da7235a807bf31ab
The AOSP builds do not have a compatible BL for Secretkeeper (24Q3+).
This leads the crashing of HAL since the backing trusty is not updated
with the TA.
Test: lunch aosp & non-aosp targets -> get_build_var SECRETKEEPER_ENABLED
Bug: 350482613
Change-Id: I49d30914bc7a4b2b752a6d9eb7db0e7959638d98
The build flag PRODUCT_BOOTS_16K will be used to select
the proper efs rc file and fstab:
- When PRODUCT_BOOTS_16K := true, 16k rc files and fstab will be used.
- When PRODUCT_BOOTS_16K := false, 4k rc files and fstab will be used.
Bug: 346868433
Test: Built Pixel 8 targets
$ source build/envsetup.sh
$ lunch husky_pgagnostic-trunk_staging-userdebug
$ get_build_var DEVICE_PAGE_AGNOSTIC
$ get_build_var TARGET_KERNEL_DIR
device/google/shusky-kernels/6.1/trunk-12010727/16kb
$ get_build_var TARGET_BOARD_KERNEL_HEADERS
device/google/shusky-kernels/6.1/trunk-12010727/kernel-headers
$ get_build_var PRODUCT_BOOTS_16K
true
$ get_build_var TARGET_RW_FILE_SYSTEM_TYPE
ext4
$ get_build_var TARGET_USERDATAIMAGE_FILE_SYSTEM_TYPE
ext4
Flag: EXEMPT bugfix
Change-Id: I4dba20518925a176f1e1e66596e2bb1e8ade7c26
pgagnotic targets might boot into 16KB directly(w/o dev options),
in which case it would need copy efs files support to be enabled.
Test: boot device with dev option disabled, check efs
Bug: 346275905
Change-Id: If18bfa0b0646da8008c6d92bec094b236273cbfc
This commit establishes a soong config variable `sim_count` for
easier converting Android.mk to Android.bp when dealing with multiple
SIMs.
Bug: 343823190
Test: presubmit
Change-Id: I93d355e30771868f1c4664eebbce579e1e37cdcb
Previously, we rely on mount points to copy files out of
efs partitions. Switch over to dump.f2fs to read directly
from block device without mounting. This allows us to copy
files out of efs partition in both 4K and 16K mode.
Test: Boot dev option enabled ext4 device
Bug: 340965747
Change-Id: I9d3f3d5200adc31f13298488b5be068b0fe7c7f4
Products using 16KB kernel may wish to boot into 16KB mode
directly. To do this, these targets would need to use ext4
as their default fs type for /data and /metadata . Add
a build time flag which would install ext4 fstabs.
Test: th
Bug: 339337171
Change-Id: I53de1599bbff583b45ca2bf6d3e3efb83957913e
During boot, this CL adds the following sequence of actions:
1. mount original efs partitions(most likely f2fs) on /mnt/vendor/efs
2. copy files in /mnt/vendor/efs to /data/vendor/copied/efs.img
3. fsync all the files in /data/vendor/copied/efs.img
4. rename /data/vendor/copied/efs.img to /data/vendor/copied/efs
5. bind-mount /data/vendor/copied/efs to /mnt/vendor/efs
6. repeat 1-5 for efs_backup and modem_userdata
The original EFS partitions are mounted and only used for file
copying, no destructive action done on original efs partitions.
Test: reformat /data as ext4, boot the device
Bug: 319335586
Change-Id: Ide78be316778acfc5c582c4a7b78853796cf4c1e
Revert submission 26822004
Reason for revert: Potential culprit for b/339099720- verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Reverted changes: /q/submissionid:26822004
Change-Id: Ie9598a3b3b56c8ce26f475079798c44314696f44
During boot, this CL adds the following sequence of actions:
1. mount original efs partitions(most likely f2fs) on /mnt/vendor/efs
2. copy files in /mnt/vendor/efs to /data/vendor/copied/efs.img
3. fsync all the files in /data/vendor/copied/efs.img
4. rename /data/vendor/copied/efs.img to /data/vendor/copied/efs
5. bind-mount /data/vendor/copied/efs to /mnt/vendor/efs
6. repeat 1-5 for efs_backup and modem_userdata
The original EFS partitions are mounted and only used for file
copying, no destructive action done on original efs partitions.
Test: reformat /data as ext4, boot the device
Bug: 319335586
Change-Id: I4c4024b4cad18199226f5644f98254b2230574d6
Add the flag "use_lassen_modem" for bp to do the same checking like
"USES_LASSEN_MODEM" in mk.
Bug: 330654744
Test: 1. lunch aosp_cheetah-trunk_staging-userdebug
2. m RilConfigService
Change-Id: I4ef0fe469e98fa6315896bbe8c422f741e207664
Next CLs in this stack will make changes to persist/efs mount process
This CL will first move relevant code to a separate file for easier
review.
To support booting under 16K page size, we need to copy files on
persist partition(F2FS, which does not support 16K page size)
to data partition(which will would be EXT4 for dev option enabled
devices).
Bug: 319335586
Change-Id: I2750eb8b53431037cecc972448799409345f5ca3
Revert submission 26384060-c2aidl-pixel-enable
Reason for revert: Culprit for b/335892284. Will be verifying through ABTD for confirmation and before submitting the revert.
Reverted changes: /q/submissionid:26384060-c2aidl-pixel-enable
Change-Id: I7b331a48f64b89a19fcedeeae783fe8fc83c22c2
