qualcomm-linux

@qualcomm-linux source repo

14 skills
0 followers
10 hours ago last updated

▌
Qcom Flash Qdl · qualcomm-linux bundle
Flash a Qualcomm Linux qcomflash image bundle onto a board in Emergency Download (EDL) mode using the QDL tool, including multi-board selection via --serial. Use when asked to "flash the board", "flash the RB3 Gen2 / rb1 / EVK", "flash the qcomflash image", "reflash over EDL", or when a device shows up as USB 05c6:9008. Do NOT use for building images (see qcom-yocto-build-image), for boot validation after flashing (see qcom-boot-validate), or for fastboot/U-Boot based flows.

0 installs
▌
Qcom Device Info · qualcomm-linux bundle
Print a concise summary of the Qualcomm Linux device this runs on: board model and SoC (device tree + socinfo), OS release including BUILD_ID, kernel, uptime and systemd state. On request, produce a full release report instead: firmware inventory from qcom_socinfo, UEFI version from the EFI loader variables, Yocto layer revisions from /etc/buildinfo, consistency findings and a release fingerprint — the QLI 2.x Ver_Info.txt replacement. Use when asked to "print device info", "what board/SoC is this", "which image/build is this board running", "release report", "what firmware is on this board", "which meta-qcom commit built this image", "reconstruct Ver_Info", or to capture a baseline before tests. Read-only; runs on the booted target, or offline on a capture someone pasted. Do NOT use for health diagnostics or host-side build questions (see qcom-yocto-build-image). This is an example skill and the authoring template for this catalog.

0 installs
▌
Qcom Boot Validate · qualcomm-linux bundle
Validate that a Qualcomm Linux board boots to a working login shell by watching its serial console: wait for the login prompt, log in with the image's default credentials, and check uname, /etc/os-release (incl. BUILD_ID) and systemd state, reporting BOOT-VALIDATION: PASS/FAIL. Use after flashing, when asked to "validate the board boots", "check the board over serial", "did the new image come up", or "watch the boot console". Needs the serial console attached to this host (or reachable over ssh). Do NOT use for flashing (see qcom-flash-qdl) or for diagnosing a healthy-but-degraded system.

0 installs
▌
Qcom Deb Flash Boot · qualcomm-linux
Flash a Qualcomm Linux Debian image from qcom-deb-images onto a board over EDL/QDL (UFS, eMMC, or the whole-disk rawprogram-ufs.xml path), write a disk-sdcard.img to an SD card, or boot a disk image locally under QEMU with scripts/run-qemu.py, then log in as debian/debian. Use when asked to "flash the Debian image", "flash qcom-deb-images to the RB3 Gen2 / RB1", "boot the Debian image in QEMU", "run the trixie image", or "write the SD card image". Do NOT use for Yocto/QLI qcomflash bundles (see qcom-flash-qdl), for building the Debian image (see qcom-deb-build-image), or for serial boot validation of a physical board (see qcom-boot-validate).

0 installs
▌
Qcom Deb Build Image · qualcomm-linux
Build a Qualcomm Linux Debian image (trixie by default, forky also supported) from qcom-deb-images using its debos recipes and Makefile targets: rootfs.tar, disk-ufs.img / disk-sdcard.img, and the flashable flash_<board>_<storage> asset directories, with optional local kernel / U-Boot debs and desktop/overlay options. Covers most QLI PoR boards (RB1, RB3 Gen 2, the ride and EVK kits) and the Arduino Qualcomm boards (UNO Q, VENTUNO Q). Use when asked to "build a Debian image for the RB3 Gen2 / RB1 / UNO Q", "build qcom-deb-images", "make a trixie image for a Qualcomm board", "build the debos image", or "build disk-ufs.img". Do NOT use for Yocto/QLI images (see qcom-yocto-build-image), for flashing or QEMU-booting the result (see qcom-deb-flash-boot), or for the standalone kernel cross-build (see qcom-kernel-qcom-next-build).

0 installs
▌
Qcom Skills Contribute · qualcomm-linux bundle
Turn local edits to an installed qcom-linux-skills skill into an upstream contribution: find the catalog clone behind the installed skill, validate the change, create a topic branch with a DCO-signed meta-qcom-style commit, and prepare (optionally open) the pull request. Use when asked to "upstream my skill changes", "propose this skill change back", "send my skill fix as a PR", or "contribute this skill improvement to the catalog". Only for changes to skills from this catalog; do NOT use for pull requests to meta-qcom or other target repositories (prepare those with qcom-yocto-pre-pr-checks).

0 installs
▌
Qcom Yocto Build Image · qualcomm-linux
Build a Qualcomm Linux (Yocto) image from meta-qcom with kas-container, composing ci/<machine>.yml with optional distro and kernel overlays, and locate the flashable qcomflash artifact it produces. Use when asked to "build an image for the RB3 Gen2 / ride-sx / IQ EVK", "build qcom-console-image", "build meta-qcom", "do a qcom-distro / sota build", or "build with the qcom-next kernel". Do NOT use for Debian images (qcom-deb-images), for flashing (see qcom-flash-qdl), or for running pre-PR checks (see qcom-yocto-pre-pr-checks).

0 installs
▌
Qcom Yocto Pre Pr Checks · qualcomm-linux
Run meta-qcom's CI-parity checks locally before opening or updating a pull request: yocto-patchreview, yocto-check-layer and oe-selftest via the ci/ helper scripts, plus a commit-message review against the project's conventions. Use when asked to "run the pre-PR checks", "check if my meta-qcom branch is ready for a PR", "run patchreview / check-layer / oe-selftest", or "validate my layer changes like CI would". Do NOT use for building images (see qcom-yocto-build-image) or for hardware validation (see qcom-boot-validate).

0 installs
▌
Qcom Yocto Lava CI Report · qualcomm-linux bundle
Produce a self-contained HTML CI/CD reliability report for a meta-qcom family layer (meta-qcom, meta-qcom-distro, meta-qcom-3rdparty) over a window of days: sweep every LAVA job the layer's CI submitted plus the GitHub Actions runs that built the images, separate real platform failures from test-harness artefacts and lab faults, quantify coverage lost to silent skips, and close with follow-up suggestions split by owner. Use when asked to "report on CI health", "why is CI so red", "analyse the last two weeks of LAVA results", "which boards are flaky", "where are we losing test coverage", or "what should we fix to stabilise CI". The skill reports and suggests only, it never edits a test suite or a layer. Do NOT use it to root-cause a single LAVA job from its URL or ID (see qcom-lava-log), or to run meta-qcom's CI-parity checks before opening a pull request (see qcom-yocto-pre-pr-checks).

0 installs
▌
Qcom Kernel Qcom Next Build · qualcomm-linux
Cross-build the qualcomm-linux kernel (qcom-next branch) standalone on an x86 host: arm64 defconfig with the prune.config + qcom.config fragment merge used by meta-qcom's linux-qcom-next recipe, producing Image, DTBs and modules. Use when asked to "build the qcom-next kernel", "compile the Qualcomm kernel", "build a kernel with my patch for a qcom board", or "enable a kernel config for qcom". Do NOT use for building complete images (see qcom-yocto-build-image) or for bumping the kernel SRCREV in meta-qcom recipes.

0 installs
▌
Qcom Yocto Update Base Lock · qualcomm-linux bundle
Refresh the upstream layer commit pins in meta-qcom's ci/base.lock.yml to the latest commit on each layer's branch and produce a changelog-style commit (one "Relevant changes for <layer>:" section per bumped layer), like commit ddbe6a6a "ci: base.lock: update layers to latest". Use when asked to "update base.lock to latest", "bump the layer hashes/revisions", "update the layers to latest", or "refresh ci/base.lock.yml" in the meta-qcom repo. git-only (no kas); touches only repos already pinned in the lock; commits on a branch and stops before push.

0 installs
▌
Qcom Yocto Download Prebuilt · qualcomm-linux
Download prebuilt Qualcomm Linux (Yocto/QLI) flashable images from the public CodeLinaro archive for supported boards (RB3 Gen 2, IQ-615, IQ-8275, IQ-9075, IQ-X5121, IQ-X7181), picking release, distro (qcom-distro / qcom-distro-sota) and image variant, then staging the extracted flashables for QDL. Use when asked to "download a prebuilt image", "get the QLI image for the IQ-9075 / RB3 Gen 2", "fetch the multimedia image", or "get flashable binaries without building". Do NOT use for building images yourself (see qcom-yocto-build-image), for flashing (see qcom-flash-qdl), or for Ubuntu/Debian images.

0 installs
▌
Qcom Kernel Platform Backport · qualcomm-linux bundle
Backport upstream board/platform enablement into the qualcomm-linux kernel LTS branch (qcom-6.18.y): identify the commits a platform needs, cherry-pick them preserving authorship under the UPSTREAM/BACKPORT/FROMGIT prefixes, prove no other platform regresses, validate on hardware, and open the pull request. Use when asked to "backport board support to 6.18", "get <board> working on the LTS kernel", "identify the patches to backport for <platform>", or "prepare a kernel PR for <board>". Do NOT use for a plain standalone kernel build (see qcom-kernel-qcom-next-build), for bumping a meta-qcom kernel SRCREV, or for building a full image (see qcom-yocto-build-image).

0 installs
▌
Qcom Lava Log · qualcomm-linux bundle
Fetch and analyze LAVA test job logs, metadata, results, and definitions from a Foundries/Linaro LAVA instance (default lava.infra.foundries.io). Use when given a LAVA job URL or job ID (e.g. .../scheduler/job/256592) and asked to investigate a test failure, root-cause a job, or read the serial console / kernel boot log. The LAVA web UI is behind Anubis anti-bot protection so WebFetch returns 403 — use the REST API endpoints below instead.

0 installs

14 published skills