The makefile logic in this file is identical to the logic required for
akita-trunk_staging-userdebug. Hence, this logic is moved to
device/google/zuma/BoardConfig-16k-common.mk to avoid duplicating the
file for akita.
Bug: 370842132
Bug: 349877551
Test: Built and booted up `aosp_shiba` and and `aosp_shiba-pgagnostic` targets
Flag: EXEMPT bugfix
Change-Id: I80cb3e9f4c4a1609ca668af554d930edb3b4c5a0
Merged-In: I80cb3e9f4c4a1609ca668af554d930edb3b4c5a0
TARGET_ build variables MUST NOT be set up in device*
files. In the device* files, the PRODUCT_ variables are not
defined properly and only after the build system finishes
parsing all the product files, we can set up TARGET_ vars
based on PRODUCT_ vars. During the parsing of the BoardConfig
files, the PRODUCT_ vars are defined and their values can
not be changed.
Test: Built and booted up `aosp_shiba` and and `aosp_shiba-pgagnostic` targets
Bug: 370842132
Bug: 350529323
Bug: 346868433
Flag: EXEMPT bugfix
Change-Id: Ic1da7f21b696f1659ef7d7b0b7089c3d2c03103e
Merged-In: Ic1da7f21b696f1659ef7d7b0b7089c3d2c03103e
The build flag PRODUCT_BOOTS_16K will be used to select
whether the shusky devices boot with 16kb kernel or 4kb kernel.
Bug: 370842132
Bug: 346868433
Test: Built and booted up the following targets:
aosp_shiba_pgagnostic-trunk_staging-userdebug
aosp_shiba-trunk_staging-userdebug
Flag: EXEMPT bugfix
Change-Id: Ia75c7f8cfca6d651777c730a3f86715a0991fbec
Merged-In: Ia75c7f8cfca6d651777c730a3f86715a0991fbec
TARGET_RW_FILE_SYSTEM_TYPE is used to decide the fstab configuration to
use for RW files. It must be set to ext4 for targets that boot with 16k
page size kernels.
Test: $ get_build_var TARGET_RW_FILE_SYSTEM_TYPE
ext4
Also built & booted the targets successfully (on internal branch)
Bug: 358213765
Change-Id: Ia4e36e5a5e10ff10e4d43c1089f8a98a3ac601b5
Flag: EXEMPT bugfix
Bug: 362710464
Flag: EXEMPT vendor configuration patch.
Test: b/362710464 verified the GPS function and time synchronize.
Change-Id: I6b7470db5d6f27f5a064ea8a7bd822b0a63b2b6e
am skip reason: Merged-In Ibec4f0c908089ca4304e59e9d37529fa2d4fa40d with SHA-1 ea3a914a03 is already in history
Original change: https://android-review.googlesource.com/c/device/google/shusky/+/3258471
Change-Id: Ic1ad5c66fa0224b6b4fa5d95a01583e237b0c2bb
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ibec4f0c908089ca4304e59e9d37529fa2d4fa40d with SHA-1 ea3a914a03 is already in history
Original change: https://android-review.googlesource.com/c/device/google/shusky/+/3258471
Change-Id: I1ae928e12c1a3313331d323e138b1b1b2d7b1ae2
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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>
The big core mask on zuma should be 0x100.
Bug: 248621289
Test: build pass
Flag: NONE powerhint change does not support flags
Change-Id: Id9dbd933505d3eaa2553ed1851883a3042028f16
Some frequencies uses unavailable frequency other soc ex: ag/22293847, the patch update them to explicitly show the actual actions of driver.
Bug: 361294204
Change-Id: I1adc41aca636650b4eaad179d73bde030146347c
FLAG: NONE powerhint do not need flag
