But here lies the rub: While the chip is natively ARM64, official Linux mainline support remains a patchwork quilt. In this post, we’ll unpack what it takes to get an ARM64 Linux distribution (or a custom Android GKI kernel) running on MSM8953, focusing on the driver stack, missing pieces, and community solutions.
This is standard ARM IP. The MSM8953 uses – enable ARM_GIC in your defconfig. No surprises here.
When configuring the kernel for MSM8953, several flags must be enabled:
The Cortex-A53 architecture enforces strict alignment rules. Older 32-bit Qualcomm downstream drivers often cast arbitrary memory pointers to structures. When updating these drivers to an ARM64 mainline environment, such casts will trigger alignment faults ( SIGBUS ) or unexpected behavior due to pointer sizing changes (32-bit long vs. 64-bit long ). Ensure all structure padding matches the 64-bit ABI using explicitly sized types ( u32 , u64 , uintptr_t ). 6. Debugging Drivers on MSM8953 Hardware msm8953 for arm64 driver
The display driver for MSM8953 was responsible for managing the MDP (Mobile Display Processor) and DSI (Display Serial Interface). It had to handle complex tasks such as dynamic refresh rates, resolution negotiation, and power management for the screen. Because this driver was deeply intertwined with the proprietary "firmware" loaded onto the Adreno GPU, open-source support was historically fragmented. For years, developers porting newer versions of Android to MSM8953 devices struggled with "fragmentation" issues where the kernel driver expected certain firmware blobs that were incompatible with newer userspace graphics libraries.
UCM (Use Case Manager) configs are stable for voice and media. Storage/SD Card: Fully functional. Sensors: Accelerometer and gyroscope are often supported. Working with Limitations
If you are looking to understand or implement , this guide covers the architectural essentials, the role of the Device Tree, and the current state of mainline Linux support. Understanding the MSM8953 Architecture But here lies the rub: While the chip
Utilizes the msm DRM/KMS driver in upstream Linux, requiring complex memory allocation (ION or DMA-BUF) and power management configurations.
# wcnss_service present in /vendor/bin/hw/ (should be 32-bit) # ensure wlan.ko is built with CONFIG_ARCH_MSM8953=y
Here's a simple example of a kernel module that interacts with the MSM8953 processor on ARM64: The MSM8953 uses – enable ARM_GIC in your defconfig
KDIR ?= /path/to/your/msm8953/kernel/source obj-m += msm8953_custom_mod.o all: make -C $(KDIR) M=$(PWD) ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- modules clean: make -C $(KDIR) M=$(PWD) ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- clean Use code with caution. Module Initialization Blueprint
: Usually caused by a mismatch between what the driver expects and what the Device Tree supplies.
export ARCH=arm64 export CROSS_COMPILE=aarch64-linux-gnu- # Configure the kernel using the specific defconfig make msm8953_defconfig # or qcom_defconfig for mainline kernels # Build the kernel image along with device tree blobs (.dtb) and modules make -j$(nproc) Image.gz dtbs modules Use code with caution.
