メニュー
Use for building U-Boot artifacts for QEMU firmware boot testing, including defconfig selection, cross compile variables, SPL/TPL, U-Boot proper, FIT or ITB files, BL31 or TF-A dependencies, logs, hashes, and provenance.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use as the first step for any non-trivial QEMU task. Produces a small implementation or debugging plan under a .oh-my-qemu task workspace with acceptance criteria, scope boundaries, artifact policy, and verification gates.
Use for QEMU board, SoC, machine, memory map, boot path, FDT/ACPI, and IRQ topology modeling. Extends qemu-plan and qemu-rlcr-loop; board work must add or extend qemu-qtest coverage for verification.
Use for booting Linux in QEMU through either direct kernel loading or firmware and bootloader stages, selecting the path from task inputs while preserving provenance, boot logs, debug handoff, and verification evidence.
Use for QEMU peripheral, accelerator, MMIO, qdev, or SysBusDevice modeling. Extends qemu-plan and qemu-rlcr-loop; register-bank modeling must use QEMU's registerinfo framework and qtest verification.
Use for adapting a QEMU TCG host backend, including optional op support, constraints, register allocation, host code emission, qemu_ld/st, atomics, and vector ops. Extends qemu-plan and qemu-rlcr-loop.
Use for adding, reviewing, or debugging a guest ISA instruction in a QEMU TCG frontend. Extends qemu-plan and qemu-rlcr-loop; this skill only defines frontend decode/translation decisions.
SOC 職業分類に基づく
| name | qemu-uboot-build |
| description | Use for building U-Boot artifacts for QEMU firmware boot testing, including defconfig selection, cross compile variables, SPL/TPL, U-Boot proper, FIT or ITB files, BL31 or TF-A dependencies, logs, hashes, and provenance. |
Use this primitive when a QEMU task needs U-Boot, SPL, TPL, FIT, ITB, or firmware-chain artifacts.
This primitive owns only U-Boot build actions and output evidence: defconfig, toolchain, external inputs, build command, logs, boot-stage artifacts, and hashes. It consumes a U-Boot source tree and build goal supplied by the caller and does not choose provenance, image packaging, or boot workflow steps.
Record:
spl/u-boot-spl, u-boot, u-boot.bin, u-boot.itb, or platform-specific combined images;Use local documentation first. Typical U-Boot patterns are:
make O=<out> <board_defconfig>
make O=<out> CROSS_COMPILE=<prefix> -j$(nproc)
If a firmware chain requires environment variables such as BL31, record their resolved paths and hashes before building.