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
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
This reduces the amount of computation needed on critical
boot path for F2FS devices. Boot time is expected to improve
with this patch.
Bug: 341216848
Test: boot device with ext4 and f2fs
Change-Id: I7311a22a7bf9773d3909656d98cc578a43cb9477
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
Common fstab entries(everything but /metadata and /data) are
moved to a separate fstab file.
This allows us to create an ext4 variant of the same fstab later.
Test: device boots
Bug: 339337171
Change-Id: I3129551c98b14473c776f2cf3dee1b81fc0c84b3
V12 is not frozen yet. We should still allow V11 for `next` build.
Test: trigger test build
Bug: 309897479
Bug: 303162192
Change-Id: I14582a51cde66698013b275ec1d668f858ad7cba
Signed-off-by: Leo Chen <yinchiuan@google.com>
Since /persisit was previously mounted during eraly-init stage,
this CL delays the /persist mount to post-fs-data stage.
Actions which depends on the /persist partition are also moved.
Bug: 319335586
Change-Id: I6bcc775f16331905c6896f3a2ec5bbea9e20744f
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
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: I744fccbf1aacd817ca1a0c6f4a121393307c8797
Since /persisit was previously mounted during eraly-init stage,
this CL delays the /persist mount to post-fs-data stage.
Actions which depends on the /persist partition are also moved.
Bug: 319335586
Change-Id: I0e70f672b9a5f4b05b95dd30b0a74bb8f91f399a
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
When a user opts into 16K developer option, we would need to convert the
/data and /metadata partition into ext4. Add necessary fstab entries for
ext4 so that zuma devices can boot on ext4.
This CL does not automatically switch existing devices to ext4, the
newly added fstab entries are intentionally marked as "non-formattable",
so that we don't accidentally format a wiped device as ext4. This CL
merely allows the device to boot if the /data partition is already
formatted as ext4.
Test: adb shell cmd recovery wipe ext4 , make sure device boots
Bug: 293313353
Change-Id: I3a2a2e9d09cdea884f58b509a06c6829938dc369
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
Placing the fips140.ko at the same level as other kernel modules makes
it easier for automation tools to handle all of them.
Bug: 331791671
Change-Id: Id6d978afbd18f98f2a07d418c405699885c05bf0
Signed-off-by: Qian-Hao Huang <qhhuang@google.com>
am skip reason: Merged-In I9f0d29ef69dc88cb8e876e37aac09ed7331c79b7 with SHA-1 f8c54e9912 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/27046269
Change-Id: Ifa42ada09fb3d458c02ab9e9f4e3e582b9bc2969
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I9f0d29ef69dc88cb8e876e37aac09ed7331c79b7 with SHA-1 f8c54e9912 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/27046269
Change-Id: I19412558e18de4d9c4ea4db61abefb24250ab092
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ia134e6b6b8dc0c9db35bcf36bed700b67466f353 with SHA-1 a4b4967c03 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/27095803
Change-Id: I9dd62a738903955b528b09043c52f6c4d6375b26
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I91039ce3a8ee4630a76113ef7ae6be3bc6908f64 with SHA-1 c0f9207cf5 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/27095802
Change-Id: I467d0bf7a406567daacc4331ad5ff246e3142279
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Reporting learning(relaxation) and model loading once a day
* learning and model loading path moved from uevent to
sysfs collector.
Bug: 329124192
Signed-off-by: Chungro Lee <chungro@google.com>
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:c0f9207cf5ad3b04ac4c64c844ab85c4a6803aab)
Merged-In: I91039ce3a8ee4630a76113ef7ae6be3bc6908f64
Change-Id: I91039ce3a8ee4630a76113ef7ae6be3bc6908f64
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
