Some OEMs add their own properties to avoid merging incompatible
overlays for different devices with the same QCOM soc.
Change-Id: Ic5b38a122173d8e9ecc1f0f399411cb37acf3150
For targets that uses mainline kernel, the kernel tree usually only
contains configs on top of the upstream repository.
In such case, if we put the configs in elsewhere, we can simply just
track the upstream kernel repo, without needing to import configs.
Example usage:
TARGET_KERNEL_CONFIG_EXT := \
$(COMMON_PATH)/kconfig/platform_defconfig \
$(COMMON_PATH)/kconfig/common-addons.config
TARGET_KERNEL_CONFIG_EXT += \
$(DEVICE_PATH)/kconfig/device.config
Change-Id: I021ffb76d0c0612343cff7b5c81541c2b88ef7e6
* Many Qualcomm targets that uses boot header v0 or v1
have the DTBs appended to the end of kernel image.
* In downstream msm kernels up to msm-4.19, Appending DTBs
is handled in the kernel tree. However, on msm-5.4 and
newer msm kernels, and on mainline kernel, This is not
supported.
* Normally, DTB processing depends on how the bootloader
loads it and should not be handled in the kernel tree,
so we handle it here.
* Instead of appending all DTBs by default, Get the list of
DTBs that needs to be included from a variable, so that
we don't need to modify dts Makefile to exclude unwanted
DTBs, and we could also ensure the DTBs are appended in
a specific order.
Change-Id: I603d1ebac5ee808bad045b85f9868d572d52cb80
Originally, BOARD_RECOVERY_RAMDISK_KERNEL_MODULES_LOAD was used, but
BOARD_RECOVERY_KERNEL_MODULES_LOAD is what build/make uses. Use the
proper variable by default and if it's not set, use the old variable.
Change-Id: I3522e4782ae56f67e49b234236fbb86c8ec65b92
This reverts commit d6777fa812.
Reason for revert: The soong namespaces can be removed after reworking
libfmjni to use select() with filegroups and header libs for qcom/slsi.
Broadcom is not used in any recent shipping device and mtk can continue
using prebuilt for now.
Change-Id: I078b321c7c55c3d7e5cd97e2664208c3d44f513a
Only signed GKI modules are permitted to export symbols listed in the
android/abi_gki_protected_exports file. Attempting to export these
symbols from an unsigned module will result in the module failing to
load, with a 'Permission denied' error message.
Change-Id: Ie15b00a6c288eda21b319eb0f735cf4f9e6e7933
modprobe won't lookup system_dlkm modules.dep when GKI modules are
required by vendor modules, so they'll fail to load.
Fixes: 259906daef ("kernel: consider gki modules when running depmod for vendor modules")
Change-Id: Ia5a77df91d84c78f76a03910178cc86db48724c8
Incorporate the hash of a combination of all msm-ids, board-ids, and
pmic-ids of the InnerMergedDeviceTree in the final filenames of the
saved InnerMergedDeviceTrees.
Change-Id: I629e1a274b23d71061c547578d1ddbcf92c8cf79
Signed-off-by: Guru Das Srinagesh <quic_gurus@quicinc.com>
Use the logging module to log important information to various log
levels: info, debug, warning and error.
- Modify __str__ representations of classes DeviceTree and
InnerMergedDeviceTree for readability in debug logs
- Make parse_dt_files() return instead of yield so as to order all the
filename parsing at one go after the preceding log messages
Use the argparse module to specify script arguments cleanly. Also make
the corresponding change to merge_dtbs.sh to invoke this script with the
correct flags.
Change-Id: Id09d9d7b34cde60eff99876f0c0c4f6643852aee
Signed-off-by: Guru Das Srinagesh <quic_gurus@quicinc.com>
When debugging issues with the script, it helps to not have in the
script's output the fully qualified path names of the DTB and DTBO files
being merged as they are very lengthy. Retain only the relevant parts of
the filnames - the basenames for better readability.
Change-Id: Ia18584fcf9ff173c4b22d4543c83c4091e15b8f8
Signed-off-by: Guru Das Srinagesh <quic_gurus@quicinc.com>
It was caused by package-cache in case Build.VERSION.INCREMENTAL
doesn't change across builds, which is always the case for local
builds, exporting BUILD_NUMBER to something != eng.$USER will fix
it the next build.
Change-Id: Ic602197e6711ced511a0b102b1140c5db4ec8397
Kernel 6.6 is not currently set up for CONFIG_NETFILTER_XTABLES_COMPAT,
breaking 32-bit iptables userspace.
Change-Id: I79823ea1c66d841f204a1d3c241619abb51f9040
Some devices have the same codename but shipped a long time
ago and may not have a current branch set up.
Continue looking up all repositories until a match is found
or no repos are left to check.
For example:
- android_device_amazon_thor
- cm-14.1
- android_device_xiaomi_thor
- lineage-21.0
- android_device_semc_zeus
- jellybean
- android_device_xiaomi_zeus
- lineage-21.0
- android_device_amazon_otter
- cm-12.1
- android_device_shift_otter
- lineage-21.0
Change-Id: Icf9826b31efd872363fdfe73d5a71ff2d06cbe20
Signed-off-by: Alexander Martinz <amartinz@shiftphones.com>
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
