marfrit
95be39ef80
Reference the 3 patches imported in the previous commit under the scope-tagged patch list. Apply order is strict (0001 → 0002 → 0003). Verified 2026-05-18 via the arch_vp9_test extlinux boot on ampere: - VP9F enumerates on rkvdec /dev/video2 - kdirect decode bit-exact vs libavcodec SW reference at -ss 30 - libva decode (firefox/chromium-style consumer) also bit-exact - vainfo lists VAProfileVP9Profile0 (iter38 multi-device probe auto-picks) - All three paths agree on sha c8624d7c42db66525f53a02a515bc38d0a17ef39f692660cc7bebb1e2d2e1b48 Removes VP9 from the "explicitly not included" comment block — issue #12 closes with this change. Also: AV1 stays out-of-scope per issue #6 ask 3 (kernel side fine via the existing av1-vpu-dec node; backend just needs the 4th-fd generalization tracked in libva-v4l2-request-fourier#2). The next linux-ampere-fourier package rebuild from this manifest will pick up VP9 automatically; ampere's running 7.0.0-rc3-vp9-test+ kernel already has these patches via the operator's manual build session today.
fleet/
Per-host manifests. One YAML per fleet member opting in to kernel-agent.
Each manifest pins:
- baseline kernel tree + ref
- scope-tagged patch includes (resolved against
../patches/) - config strategy
- package naming + install mode (alongside / replace)
- verification bars (which of Bar 1..5 apply)
- build host routing
- backup target
Manifest is the single source of truth. Running state may drift; drift is informational, not blocking. ka-status reports per-host drift.