Hi all,
I’ve been following the progress of ARM64 laptop support in mainline Linux, and I wanted to start a discussion around what is still missing or blocking “daily-driver” readiness for AArch64 laptops.
From my understanding, a lot of core functionality has improved significantly in recent years (especially around basic boot, display, and some device support), but there still seem to be gaps depending on the hardware platform.
Some areas I’m curious about:
Power management and suspend/resume stability across different ARM laptop platforms GPU acceleration consistency (especially across Adreno-based devices) WiFi / Bluetooth reliability and upstream driver maturity Audio stack issues and device-specific quirks Firmware/boot flow inconsistencies (UEFI vs DT vs vendor boot chains) Overall fragmentation between different ARM laptop implementations
It would be great to hear what others consider the current top blockers for upstream mainline usability.
I’m also working on a personal side project called Street View (https://street-view.io/), which involves mapping and exploring real-world locations in the USA. Having reliable ARM laptops for development and testing would make workflows like this much more accessible, especially for lightweight field/dev setups. That’s part of why I’m interested in understanding how close we are to stable, consistent ARM laptop support in mainline Linux.
Looking forward to hearing insights from maintainers and other contributors.
Thanks!
aarch64-laptops@lists.linaro.org