Skip to main content
Qualcomm Linux 2.0 introduces significant improvements over Qualcomm Linux 1.0 across the build system, layer architecture, kernel, device tree management, and technology stacks. The following table provides a high-level summary of the key benefits and advantages of Qualcomm Linux 2.0 compared to Qualcomm Linux 1.0: Table: Qualcomm Linux 1.0 vs. Qualcomm Linux 2.0

​
1. Simplified and unified build system (KAS-based)

The following table lists the key differences in the build system between Qualcomm Linux 1.0 and Qualcomm Linux 2.0: Benefit: Drastically reduces the number of steps to set up a build environment. Developers and CI/CD pipelines can build with a single command, reducing human error and onboarding time.

​
2. Consolidated and Cleaner Layer Architecture

The following table lists the key differences in the build system between Qualcomm Linux 1.0 and Qualcomm Linux 2.0: Benefit: Fewer layers to manage, fewer inter-layer dependencies to track, and a single source of truth for all BSP recipes. Reduces integration complexity for customers building their own layers.

​
3. Cleaner and More Transparent Image Recipe Organization

The following table lists the key differences in the build system between Qualcomm Linux 1.0 and Qualcomm Linux 2.0: Benefit: Customers can clearly see what is in each image. No more tracing complex override chains to understand rootfs content. Easier to customize and maintain.

​
4. Upstream-Aligned Kernel and Device Tree (LTS v6.18)

The following table lists the key differences in the build system between Qualcomm Linux 1.0 and Qualcomm Linux 2.0: Benefit: A single, modern LTS kernel simplifies maintenance. Upstream-aligned device trees mean better community support, easier upstreaming of customer changes, and no need to maintain downstream-only patches.

​
5. Modern FIT-Based DTB and UEFI Improvements

The following table lists the key differences in the build system between Qualcomm Linux 1.0 and Qualcomm Linux 2.0: Benefit: Adding new hardware variants is significantly easier and doesn’t require firmware changes. The FIT-based approach is an industry-standard mechanism, reducing vendor lock-in and improving long-term maintainability.

​
6. Modular Overlay Architecture (New in QLI 2.0)

QLI 2.0 introduces new Overlay system - a key architectural advantage:
  • Qualcomm value-added components (Audio, Camera, Graphics, Video, Sensors, Vision) are delivered as modular, loadable overlays.
  • Customers can start with a fully upstream image (qcom-multimedia-image) and selectively enable Qualcomm technology stacks.
  • Overlays use module blacklisting to cleanly swap upstream drivers for Qualcomm-optimized ones at runtime.
  • No need to rebuild the entire image to switch between upstream and Qualcomm stacks.
Benefit: Customers get maximum flexibility - evaluate upstream components first, then layer in Qualcomm-specific optimizations only where needed. This is ideal for product development and reduces time-to-market.

​
7. Seamless OTA Upgrade Path from QLI 1.0

  • QLI 2.0 supports the same OTA mechanisms as QLI 1.0 (OSTree for Linux + UEFI Capsule for firmware).
  • Customers can upgrade from QLI 1.0 to QLI 2.0 over-the-air without re-flashing.
  • EFI variables are now stored in the EFI partition directly (no need to run uefi_sec app manually)
Benefit: Protects existing field deployments. Customers running QLI 1.0 in production can migrate to QLI 2.0 without physical access to devices.

​
8. Simplified Container and Kubernetes Support

The following table lists the key differences in the build system between Qualcomm Linux 1.0 and Qualcomm Linux 2.0: Benefit: Cleaner separation of concerns. Container and orchestration workloads are independent of the multimedia stack, making it easier to build purpose-specific images.