So
@zacharias.maladroit whats happening how much of this rom needs to edited to fully work and how is the kernel doing?
https://forum.xda-developers.com/showpost.php?p=76479481&postcount=30
&
CONFIG_BT_MSM_SLEEP -> bluetooth driver differences
CONFIG_MSM_DCC => ?
CONFIG_QNS_SYSTEM=y
CONFIG_QUOTA=y
CONFIG_QUOTACTL=y
CONFIG_SDCARD_FS=y
CONFIG_SPLIT_PTLOCK_CPUS=999999
CONFIG_DEBUG_SPINLOCK_BITE_ON_BUG=y
# CONFIG_DEBUG_SPINLOCK_PANIC_ON_BUG is not set
CONFIG_MSM_RTB_SEPARATE_CPUS=y
CONFIG_PROC_PID_CPUSET=y
# CONFIG_QFMT_V1 is not set
CONFIG_QFMT_V2=y (quotas)
CONFIG_QUOTA_NETLINK_INTERFACE=y
CONFIG_QUOTA_TREE=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_SERIAL_MSM_HSL_CONSOLE=y
ours:
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_CSVT=y
theirs:
# CONFIG_USB_SERIAL is not set
--- /dev/null
+++ b/arch/arm64/configs/diffconfig/suzu_diffconfig
@@ -0,0 +1,7 @@
+CONFIG_MACH_SONY_SUZU=y
+CONFIG_NFC_PN547=y
+CONFIG_QPNP_SMBCHARGER_ID_POLL=y
+CONFIG_TOUCHSCREEN_CLEARPAD=y
+CONFIG_USB_MIRRORLINK=y
+CONFIG_TOUCHSCREEN_CLEARPAD_I2C=y
+CONFIG_TOUCHSCREEN_CLEARPAD_RMI_DEV=y
--- a/arch/arm64/configs/msm8994-perf_defconfig
+++ b/arch/arm64/configs/msm8994-perf_defconfig
@@ -243,13 +243,14 @@ CONFIG_PPPOPNS=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_USB_USBNET=y
-CONFIG_CNSS=y
CONFIG_WCNSS_MEM_PRE_ALLOC=y
-CONFIG_CNSS_MAC_BUG=y
-CONFIG_CLD_LL_CORE=y
CONFIG_ATH_CARDS=y
CONFIG_WIL6210=m
CONFIG_E1000E=y
+CONFIG_CNSS_PCI=y
+CONFIG_CNSS_MAC_BUG=y
+CONFIG_CLD_LL_CORE=y
+CONFIG_BUS_AUTO_SUSPEND=y
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_EVBUG=m
CONFIG_KEYBOARD_GPIO=y
diff --git a/arch/arm64/configs/msm-perf_defconfig b/arch/arm64/configs/msm-perf_defconfig
index bfe14733b104..12a8d65cf3cd 100644
--- a/arch/arm64/configs/msm-perf_defconfig
+++ b/arch/arm64/configs/msm-perf_defconfig
@@ -220,7 +220,6 @@ CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=y
CONFIG_MSM_BT_POWER=y
CONFIG_CFG80211=y
-CONFIG_NL80211_TESTMODE=y
CONFIG_CFG80211_INTERNAL_REGDB=y
CONFIG_RFKILL=y
# CONFIG_NFC_QNCI=y
@@ -270,9 +269,11 @@ CONFIG_PPPOPNS=y
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
CONFIG_WCNSS_CORE=y
+CONFIG_CNSS_SDIO=y
CONFIG_WCNSS_CORE_PRONTO=y
CONFIG_WCNSS_MEM_PRE_ALLOC=y
CONFIG_WCNSS_REGISTER_DUMP_ON_BITE=y
+CONFIG_CLD_HL_SDIO_CORE=y
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_EVBUG=m
CONFIG_KEYBOARD_GPIO=y
@@ -288,8 +289,6 @@ CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI4=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_RMI4_DEV=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_FW_UPDATE=y
CONFIG_SECURE_TOUCH=y
-CONFIG_TOUCHSCREEN_BU21150=y
-CONFIG_INPUT_MT_WRAPPER=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_HBTP_INPUT=y
CONFIG_SENSORS_MPU6050=y
@@ -305,6 +304,7 @@ CONFIG_SENSORS_ISL29044A=y
CONFIG_SENSORS_CAPELLA_CM36283=y
# CONFIG_SERIO_I8042 is not set
# CONFIG_VT is not set
+CONFIG_SERIAL_MSM_HS=y
CONFIG_SERIAL_MSM_SMD=y
CONFIG_DIAG_CHAR=y
CONFIG_HW_RANDOM=y
@@ -611,3 +611,4 @@ CONFIG_SPDM_SCM=y
CONFIG_SECCOMP=y
CONFIG_BUILD_ARM64_APPENDED_DTB_IMAGE=y
CONFIG_UID_CPUTIME=y
+CONFIG_WLAN_FEATURE_RX_WAKELOCK=y
CONFIG_WLAN_FEATURE_RX_WAKELOCK=y
that'll get you an idea:
kernel-side:
bluetooth might be a problem, we need sdcardfs, our SoC/processor might lack certain parts that are necessary for functions of the ROM (DCC "MSM data capture and compare engine" and others),
binder needs updating,
display driver (?),
matching gpu driver (kernel-side) & adreno blobs (ROM-side)
we might need different kernel modules built for the ROM & subsystems might require rework (see attached list of kernel modules)
ROM-side:
modem needs to be replaced (M-ROM 2.4.8 by nreuge has those files in system/etc/customization/modem ),
ril / qcril might need work
wlan (system/firmware/wlan/bcmdhd) firmware might need to be replaced with ours
system/etc/wifi/wifi_txpower.conf might need modification
system/compatibility_matrix.xml might need changes
where is system/etc/mixer_paths.xml ? => system/vendor/etc/
system/vendor/lib{64}/{egl} adreno related libs need to be checked out - the driver most probably won't work with kernel-side
fingerprint & nfc libraries need to be evaluated [later]
msm_irqbalance, thermal, etc. all crucial subsystems and configurations need to be
double and triple-checked before even attempting to put it on the device.
[I got a
terrifying moment today while modifying MHL driver and got
strange noises out of the phone & speaker -
better safe than sorry]
That's only a first (and most likely incomplete) pass through the ROM files