Starting with android common kernel 6.6, rust is enabled for arm64 gki.
It currently looks for rust version 1.73.0, so that was selected as the
default. This was only added for the clang compile path as gki requires
clang.
Change-Id: Ie7b57568d74cfb4a28a94c8dc8f4b5c622044317
Revert "kernel: Check HIP support of clang before disabling it"
This reverts commit 62c1374385.
Revert "kernel: Force disable LLVM HIP"
This reverts commit ef68678120.
Revert "kernel: Force disable LLVM CUDA"
This reverts commit ba14020f85.
Change-Id: I5cb2b4624eb0ec25dbc8c1b5888708d961ae59d7
Since ADDITIONAL_SYSTEM_PROPERTIES is being deprecated, this will
need to be handled in build/make and build/soong
Change-Id: Ib4925969f0d9f60ea5b30455806ff80a1817d61f
This reverts commit b538b7ca24.
Reason: Landscape lockscreen doesn't look that great with
pattern/pin in phones, its better suited for tablets
or large screen devices, its enabled by default for those.
Change-Id: Id461f73f7976e8a9c7242f0b406e700f6c06ecf4
Change I8b6040e03589bde2af4e161c891ded237a9bb335 did not account for
devices without a separate vendor partition, causing build to fail with
the following:
FAILED: ninja: '/file_list.txt', needed by 'out/target/product/joan/obj/KERNEL_OBJ/arch/arm64/boot/Image.gz-dtb', missing and no known rule to make it
Use systemimage_intermediates instead on said devices.
Test: m kernel
Co-authored-by: Bruno Martins <bgcngm@gmail.com>
Change-Id: If9eb75a1bef98345e9c137c2463e392d50be239b
- Mention the right kernel image on documentation
- Build dtbs only when the dts folder exists, Google enables CONFIG_OF
on x86_64 GKI config, this is also the same check done on Linux
Makefile
Change-Id: I1b0f7a39b0b00f2a4516d2cff79e591136ee3af8
This is required to ensure that kernel modules end up on the final
partition images when `BUILD_BROKEN_INCORRECT_PARTITION_IMAGES`
environment variable or board config variable is not set.
See 152cdfab7c
for more information.
Co-authored-by: Bruno Martins <bgcngm@gmail.com>
Change-Id: I8b6040e03589bde2af4e161c891ded237a9bb335
QPR2 introduced remaining build time in the progress box [0]
but it was broken with tee cmd so dopush() was worked fine.
Now, QPR3 fixed that issue so dopush() is broken.
Example:
[ 99% 394/395 1m30s remaining] Copy: out/target/product/devon/apex/art_boot_images/javalib/arm/boot.art
[100% 395/395 1m30s remaining] Install: out/target/product/devon/system/framework/framework.jar
Change-Id: Ifdfcfe0f750d39f4e3fe7d669e5094729d75e224
* Bypasses the literally infinite timeout for users who have
limited access to GitHub (before: 2m13.749s, after: 0m14.354s)
* The timeouts should be enough for users who have freedom internet
access, even ADSL network connection shouldn't take that long...
Test:
1. Execute `source build/envsetup.sh`
2. `breakfast` a existing device
3. Add "0.0.0.1 github.com" and "0.0.0.1 raw.githubusercontent.com"
to /etc/hosts
4. `breakfast` any device, observe that it should not take up to
minutes to quit
Change-Id: Ib90e69c75a50e66b47e6245cb6d0521351b5c71b
Some OEMs (for example: oplus) push their dtbs to their own folders which causes kernel build to error out, fix this by including non qcom dtbs as well.
Change-Id: I2f51db103475cd2609cd061e0ec66af5accb96ab
