Msm8953 For Arm64 Driver ((top)) -

CONFIG_ARM64=y CONFIG_COMPAT=y # Enables 32-bit userspace compatibility CONFIG_ANDROID_BINDER_IPC=y CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder"

# wcnss_service present in /vendor/bin/hw/ (should be 32-bit) # ensure wlan.ko is built with CONFIG_ARCH_MSM8953=y

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. msm8953 for arm64 driver

The challenge is not that MSM8953 cannot run ARM64; it’s that the proprietary driver blobs (firmware, HALs, GPU drivers for Adreno 506) were compiled for 32-bit userspace. To run a pure ARM64 system (e.g., GSI or custom ROMs with 64-bit binder), developers must either:

Booting the Mainline Linux Kernel on Qualcomm Devices | Blog Can’t copy the link right now

Getting a functional ARM64 driver stack on the MSM8953 requires moving away from the "downstream" (Android-specific) 3.18 or 4.9 kernels and toward the (current stable releases). 1. Device Tree (DT) Configuration

Connects the SoC to the PM8953 Power Management IC (PMIC). Almost every driver depends on this bus to toggle voltage regulators. 2. The Foundation: Device Tree Nodes ( .dts and .dtsi ) To run a pure ARM64 system (e

Unlike older 32-bit MSM chips, the MSM8953 boots strictly in mode. This means:

: Integrated Wi-Fi (WCN3680 or WCN3990 frameworks), Bluetooth, and GPS subsystems governed by specific low-power Qualcomm transport mechanisms (SMD/RPM). The Role of ARM64 Drivers on MSM8953

The Venus driver handles hardware-accelerated video encoding and decoding via V4L2. 3. Compiling the ARM64 Kernel

What are some difficulties in mainlining Qualcomm chip drivers into the Linux kernel?