Files
marfrit-packages/arch/linux-pinetab2-danctnix-besser/README.md
T
claude-noether 3f1a26cc1b arch/linux-pinetab2-danctnix-besser: pkgrel=4 — first kernel-agent-managed release
Migrates the danctnix-besser kernel PKGBUILD from the boltzmann-side
hand-managed flow (marfrit/besser/danctnix-besser-pkgbuild/) into this
package tree.

Contents:
  PKGBUILD     - pkgver=7.0.danctnix1 pkgrel=4, single cumulative patch
                 source (replaces the 3-patch arrangement of pkgrel=3 +
                 fixes the duplicated 0003-arm64-... source-array entry
                 bug that was present in pkgrel=3)
  config       - same SCS=n config as pkgrel=3
                 (CONFIG_SHADOW_CALL_STACK disabled per
                 reference_arm64_scs_arm_neon_gcc15 — GCC 15.2.1 build
                 trap)
  0001-bes2600-besser-kernel-agent-cumulative.patch
               - 157446 bytes, b2sum a807297b25be...
               - Generated by ka-promote ohm against
                 kernel-agent:fleet/ohm.yaml
               - Contents: hand-curated c5x cumulative + Patch I (close
                 besser#1) + xor-neon SCS-fix (no-op while SCS=n)
  manifest.lock
               - Provenance: ka-promote-recorded sha256 per included
                 patch, cumulative b2sum, manifest sha256
  README.md    - flow docs, pkgrel history, caveats

Provides:  linux-pinetab2=7.0.danctnix1-4
Conflicts: linux-pinetab2
Verified:  source contents byte-identical to working pkgrel=3 stack
           (148149 + 7735 + 1562 = 157446 = ka-promote output size).
2026-05-18 16:51:26 +02:00

53 lines
2.6 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# 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](https://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 |
|--------|------------|-------------------------------------------------|
| 13 | 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.