There are 4 partitions that are flashed at the factory and use F2FS fs with
4kb block size:
- /dev/block/by-name/efs
- /dev/block/by-name/efs_backup
- /dev/block/by-name/modem_userdata
- /dev/block/by-name/persist
These partitions can NOT be mounted by 16kb kernels because F2FS
expects BLOCK_SIZE == PAGE_SIZE.
In order to access the files in these partitions by 16kb kernels,
the dump.f2fs tool is used.
This change will perform these steps at boot time ONLY for 16kb mode. For
every partition (efs/efs_backup/modem_userdata/persist):
1. Use dump.f2fs to copy the content of the partition
to /data/vendor/copied/<partition name>.img.
2. If the copy was succesfull, rename /data/vendor/copied/<partition name>.img
to /data/vendor/copied/<partition name>
3. fsync the content of the directory /data/vendor/copied/<partition name>.
After the content of the partitions is in /data/vendor/copied,
bind-mount the partitions to the directory /mnt/vendor. See conf/fstab.efs.from_data.
Note: This change ONLY applies to 16kb kernels. This change does not modify
the original partitions.
Bug: 347015136
Bug: 362368691
Test: $ source build/envsetup.sh
$ lunch [zumapro]-trunk_staging-userdebug
$ m
$ ./vendor/google/tools/flashall -w
Flag: EXEMPT bugfix
Change-Id: Idf46a2a3a4f0b2e91ee4a0322a0c469e055684c8
The setup of the persist partition is moved to init.persist.rc.
This will make easier to configure 16kb targets in follow up
changes.
Bug: 347015136
Test: $ source build/envsetup.sh
$ lunch [zumapro]-trunk_staging-userdebug
$ m
$ ./vendor/google/tools/flashall -w
Flag: EXEMPT bugfix
Change-Id: Ifd17fc1f25ea8cf73470630e14a38116e0b7b96a
Update fstab used so that both ext4 and f2fs are supported.
Copying previously release config to zumapro to support pixel
9.
Test: atest Enable16KbTest
Flag: build.RELEASE_GOOGLE_CAIMAN_16K_DEVELOPER_OPTION
Bug: 347108593
Change-Id: I8da600ac8e91e61abc20a324762f19dddf846851
On userdebug & eng builds, change permission of SJTAG writable sysfs files that need to be written to 'system'. This became necessary after HSUM separated main user from the SYSTEM user
Bug: 367918586
Flag: EXEMPT bugfix
Test: Ensure that there is "Privileged Debugging" item in BetterBug settings.
Change-Id: Id433aea05d23841bb5b45b7b9464daa72602269b
Signed-off-by: Kostya Yarmash <kyarmash@google.com>
This variable only does something when it differs from
TARGET_CPU_VARIANT. Setting it to the same values doesn't do
anything.
Bug: 368635026
Test: presubmit
Flag: EXEMPT trivially safe build cleanup
Change-Id: Id2934bc0dcbffb85a43ab020a8208fb85f51432a
Bug: 347122505
Test: check the priority and latency of input thread in Perffeto
Flag: NONE early device setting updates
Change-Id: Ib4f7efd03bb7118b32538b569a6587f4a786ca7b
If the enumeration is too long, it may trigger the watchdog mechanism
to cause device reset. Therefore, this patch will modify the timeout.
Ported from Change-Id: Ib54d8ff5a1e680fc86f2b89ee0d02d63ee5741d8
(usb: modify the initial_descriptor_timeout to 500ms)
Bug: 365715654
Test: verified `initial_descriptor_timeout` is set to 500
Flag: EXEMPT cherry-picked CLs from existing projects
Change-Id: I36c5a0ba0a766720cd7d6601cc56f3a883adac8a
Signed-off-by: Kuen-Han Tsai <khtsai@google.com>
For PDK build, the "vendor/arm" path doesn't exist. The modules will be
built from vendor/google_devices/zumapro/prebuilts/gpu.
Flag: EXEMPT bugfix
Bug: 364491703
Test: 1. lunch comet-trunk_staging-eng
2. m libGLES_mali vulkan.mali libOpenCL libgpudataproducer
Change-Id: Ie58b2707fb9774f4a3552561b809c3c15d3803ef
This reverts commit 7e10eefc25.
Reason for revert: Re-enable EHLD since kernel EHLD issue is fixed.
Bug: 354380599
Change-Id: I588c2b96a69cabb7be8d264c9591b61da80fb5e2
std::vector<const T> uses std::allocator<const T>, which is an
undocumented libc++ extension to the C++ standard library. The extension
was removed in llvm.org/PR96319. Use an ordinary non-const T instead.
Bug: http://b/349681543
Test: m android.hardware.power.stats-impl.zumapro
Flag: EXEMPT, refactor to fix build failure
Change-Id: I96ab1eb2caf092008cc573949a1529c057ee4bb1
The 16kb kernels need to select the fstab that has this configurations:
- data partition: fstab
- metadata partition: ext4
Bug: 350101696
Test: Built zumapro target and checked mounted partitions
Flag: EXEMPT bugfix
Change-Id: I2fc82946cdbadee7af0b3f6fc026b846fa79a146
The f2fs block size has to be set up to 16384 for 16kb kernels.
Bug: 350101696
Test: Built zumapro device and checked mounted partitions
Flag: EXEMPT bugfix
Change-Id: Ie3bf17d78da62a20882b17363afeb3a3a8a984e0
The zumapro targets that only boot with 16kb kernels will
have this filesystem setup for data and metadata partitions:
- data partition: f2fs
- metadata partition: ext4
Important: For the HW file encryption to work in the data partition in 16kb kernels the `dusize_4k` parameter has to be set:
```
fileencryption=:aes-256-hctr2:inlinecrypt_optimized+wrappedkey_v0+dusize_4k
```
Bug: 350101696
Test: built pgagnostic target and checked the fs for mounted
partitions.
Flag: EXEMPT bugfix
Change-Id: I566618e6fa1db2ff4463e00e8d091e7226ba0399
This variable doesn't do anything for devices launching with
API level 26 or later, and the initial zumapro devices (Pixel 9)
launched with API level 34.
Bug: 307369186
Test: presubmit
Flag: EXEMPT trivial build cleanup
Change-Id: If23568e7e1fc0dff05467e6b4fc97376c06c2233
For PDK build, the "vendor/unbundled_google" path doesn't exist.
"GoogleDialer" will be built from vendor/google_devices/zumapro/proprietary/GoogleDialer.
Flag: EXEMPT bugfix
Bug: 364510147
Test: export USES_GOOGLE_DIALER_CARRIER_SETTINGS=true; m GoogleDialer
Change-Id: I5c6796036627a5ae208dfda3ea19ead550a55c9a
