| Branch | Yocto recipe | Use case |
|---|---|---|
qcom-6.18.y | linux-qcom_6.18.bb | LTS production builds; recommended for SoC bring-up and integration |
qcom-next | linux-qcom-next_git.bb | Upstream contribution and validation against the latest kernel |
Yocto workflow
The Yocto workflow accesses the kernel through themeta-qcom layer. The
kernel source is fetched automatically by BitBake during the build.
Get access to the following repository:
- meta-qcom (layer): https://github.com/qualcomm-linux/meta-qcom
qli-<version> convention (for example, qli-2.0). For
available tags, see the Qualcomm Linux release notes - Introduction.
Sync meta-layers with kas
Run the following commands from your workspace root directory. After syncing, the workspace contains ameta-qcom/ directory.
rb3gen2-core-kit.yml with your machine YML) and run the
unpack task:
meta-qcom/conf/machine/include/qcom-base.inc, which every machine
configuration inherits:
Select
linux-qcom for LTS BSP or linux-qcom-next for mainline BSP, with
PREFERRED_VERSION_virtual/kernel left empty.SRCREV and SRCBRANCH for each release:
- LTS recipe: recipes-kernel/linux/linux-qcom_6.18.bb
- Mainline recipe: recipes-kernel/linux/linux-qcom-next_git.bb
Standalone workflow
For the standalone workflow (kernel-only builds without a full Yocto image), clone the kernel repository:SRCREV
field in meta-qcom/recipes-kernel/linux/linux-qcom_6.18.bb.
For the full build steps, see Build the kernel without Yocto.
