marfrit-packages/arch/linux-pinetab2-danctnix-besser

linux-pinetab2-danctnix-besser

DanctNIX PineTab2 kernel + the BESser bes2600 driver patchset. kernel-agent managed as of pkgrel=4 (2026-05-18).

TL;DR

• What: drop-in replacement for linux-pinetab2 with the BESser bes2600 patchset applied.
• For: PineTab2 (RK3566) with the on-board BES2600 SDIO WiFi/BT chip.
• Install: pacman -U linux-pinetab2-danctnix-besser-*.pkg.tar.zst linux-pinetab2-danctnix-besser-headers-*.pkg.tar.zst. It provides and conflicts with linux-pinetab2, so it slots in cleanly.
• Source of truth for patches: git.reauktion.de/marfrit/kernel-agent fleet/ohm.yaml.

How the patch cumulative is built

1. kernel-agent/fleet/ohm.yaml lists the patch series-dir includes for this kernel.
2. kernel-agent/bin/ka-promote ohm walks those includes, concatenates them into a single cumulative.patch, and emits a manifest.lock recording per-patch sha256s and the cumulative b2sum.
3. The cumulative is dropped into this directory as 0001-bes2600-besser-kernel-agent-cumulative.patch, the b2sum in PKGBUILD is updated to match, and pkgrel is bumped.
4. manifest.lock is committed alongside the cumulative for an audit trail (which patches went in, in what order).

pkgrel history

pkgrel	Date	Notes
1–3	2026-05-08…05-18	hand-managed in marfrit/besser/danctnix-besser-pkgbuild/ (DEPRECATED)
4	2026-05-18	first kernel-agent-managed release; same source contents as the hand-managed pkgrel=3 (Patch I + SCS workaround folded into single cumulative); fixes pkgrel=3's duplicated 0003-arm64-...patch source-array bug

Known caveats

• CONFIG_SHADOW_CALL_STACK=n in the config: GCC 15.2.1 fails to build arch/arm64/lib/xor-neon.c with arm_neon.h #pragma GCC target() blocks and -fsanitize=shadow-call-stack. See reference_arm64_scs_arm_neon_gcc15 memory and the Makefile workaround patch included in the cumulative. Track upstream GCC resolution before re-enabling.
• The cumulative-c5x-danctnix series-dir in kernel-agent is currently a single-file interim (the working hand-curated cumulative) because the per-series mirrors created in kernel-agent#17 use DKMS-style root paths instead of in-tree staging paths and do not apply cleanly. Per-series reconstruction is a separate kernel-agent follow-up. The b2sum integrity check in PKGBUILD still pins the exact bytes shipped.