linux-ampere-fourier: bump to kafr2 (v7.0-rc3 + kernel-agent manifest, VP9 + AV1) #27
Reference in New Issue
Block a user
Delete Branch "claude-noether/marfrit-packages:noether/linux-ampere-fourier-kafr2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bumps linux-ampere-fourier to kafr2: drops the f8f3ad9 baseline (which black-screens ampere per
fleet/ampere.yamlbisect note) in favor of the kernel-agent-managed 10-patch set fromfleet/ampere.yaml.Baseline change
Patch set (exactly mirrors
fleet/ampere.yamlmanifest)10 patches between v7.0-rc3 and tip 48a8c78:
soc/rockchip/rk3588/0001-pwm15-pinctrl-entries.patchboard/coolpi-cm5-genbook/0002-pwm-fan.patchmodule/coolpi-cm5/0003-RK806-system-power-controller.patchboard/coolpi-cm5-genbook/0004-speaker-via-audio-graph-card.patchboard/coolpi-cm5-genbook/0005-USB-C-PD-via-FUSB302.patchboard/coolpi-cm5-genbook/0008-lid-switch-USB3-PHY.patchboard/coolpi-cm5-genbook/0011-wire-internal-microphone.patchdriver/media/0001-rkvdec-vp9-rename-get_ref_buf.patch(Sarma)driver/media/0002-rkvdec-move-vp9-to-common.patch(Sarma)driver/media/0003-rkvdec-vp9-vdpu381.patch(Sarma)Identical content + apply order to what
ka-promote ampereproduces as cumulative.patch (manifest.lock b2sum:ecd17897f70ee637...).Verification before PR
Hand-built equivalent (kernel
7.0.0-rc3-vp9-test+) was running on ampere when these decode checks ran:c8624d7c42db66525f53a02a515bc38d0a17ef39f692660cc7bebb1e2d2e1b4830d2091158d92f3c5e0a807217c3e7307f873267673d92632e7fb147383e7dd1Why no CI build
linux-ampere-fourier has no entry in
.gitea/workflows/build.yml— itsprebuild.shrequires$LINUX_RK3588_MARFRIT_TREE(default~/src/linux-rockchip) on the build host, which CI runners don't have. Build happens on ampere (or boltzmann) natively; the package is published viamarfrit-publishafter the local build verifies.Will mark ready-to-merge once:
linux-ampere-fourierextlinux label boots successfully🤖 Generated with Claude Code
Drops the f8f3ad9 baseline ("18 commits ahead, BLACK-SCREENS ampere" per fleet/ampere.yaml bisect note) in favor of the kernel-agent- managed 10-patch set produced by ka-promote from fleet/ampere.yaml. Baseline: mainline v7.0-rc3 (3daa4f5dc6cc), plus the 10 scope-tagged patches under marfrit/kernel-agent/patches/{soc,module,board,driver}/: - 1 soc/rk3588 pwm15 pinctrl - 6 board/coolpi-cm5-genbook DTS patches - 3 driver/media Sarma VP9-on-VDPU381 patches (PR #24 closure) New _commit 48a8c78 reflects this tree state in ~/src/linux-rockchip (branch vp9-build on ampere, exactly v7.0-rc3 + 10 manifest patches). End-to-end verified before this iteration was cut (hand-build of the same tip on 2026-05-18 booted ampere via arch_vp9_test extlinux label): - VP9 decode bit-exact HW==SW==libva (sha c8624d7c42db66525f53a02a515bc38d0a17ef39f692660cc7bebb1e2d2e1b48) - AV1 decode bit-exact HW==SW via kdirect (sha 30d2091158d92f3c5e0a807217c3e7307f873267673d92632e7fb147383e7dd1, av1-vpu-dec is mainline 7.0) prebuild.sh canonical sha256 cleared — gzip-version-dependent, the script warns-not-fails on mismatch. First successful kafr2 build can pin a canonical sha here if a reproducibility audit ever needs it. Cross-references: - marfrit/kernel-agent#12 (VP9 enablement closure) - marfrit/kernel-agent PR #24 (Sarma patch import + ampere.yaml bump)