The Android are now based on Trunk Stable world and Pixel prebuilts CLs
also needs to reply with this which controlled by the flag which results:
- the flag value might be different on each branches
- the flag value are mostly different on each release configuration
- for local builds, ENGs' needs to figure out the correct location
of current prebuilts by checking through entire prebuilt textproto
files
To alleviate this problem, create an symlink file under android root
indicates current prebuilt path after invoke the android lunch cmd.
Bug: 364831620
Flag: EXEMPT export current prebuilt path
Change-Id: I9066437856338ef7da02be5648a119c1c38cc288
Signed-off-by: Robin Peng <robinpeng@google.com>
to mitigate potential kernel panic, load g2d only at the
same time.
Test: Build pass
Bug: 287727823
Change-Id: I8b4eac1875d3b394fc9ab651959db54c53967326
Signed-off-by: Chungkai Mei <chungkai@google.com>
This reverts commit d4c206cfcf.
Reason for revert: exynos_devfreq is fixed by pa/2512847, and add 2 shiba DVT and 1 Husky DVT to reboot 5000 times, only one device hit ramdumpg with reset message "itmon triggering err_tmout from HSI1 PCIE_GEN3_0 to NOCL0_", but according to b/283930792, even without parallely module loading, device still hit this issue. so currently parallel module loading seems to be stable enough.
Bug: 285064434
Change-Id: I0356075a60cc0224ac975b401654b424ff4b993e
This reverts commit 04716d5711.
Reason for revert: Now we can enter fastbootd normally.
Test: shiba rebooted 1000 times without failure
Bug: 280112517
Change-Id: I92736b1e535468083b35058f83a91ad153b6c5c6
Move shusky thermal .json files into thermal/
and perf configs into perf/.
Also move the configs into device-shusky-common.mk,
allowing override of the config file path.
Bug: 277993984
Change-Id: Ifa2882ee9c27c57d967c27f9f8e8edaff313e2d5
Disable parallel module loading.
iommu driver loading parallel prevented boot to
fastbootd.
resolved with
fastboot oem cmdline set samsung-sysmmu-v9.load_sequential=1
disabling all parallel module loading for now, can re-enable
at a later stage with verification.
Bug: 268269286
Change-Id: Iccecff4ae552567f3a5fb8a421b8e1993657fbc7
Copied from R4 display config file with disabling auto brightness
because ambient light sensor on ripcurrent dev board might not be
working.
Bug: 243634950
Test: check display brightness after fastboot -w
Change-Id: I45c4084d94330a3cd0fa147c6cbc10b430d44906
Signed-off-by: Shiyong Li <shiyongli@google.com>
