marfrit
e2991ff55b
build and publish packages / distcc-avahi-aarch64 (push) Successful in 6s
build and publish packages / mesa-panvk-bifrost-aarch64 (push) Successful in 5s
build and publish packages / mesa-panvk-bifrost-video-aarch64 (push) Successful in 5s
build and publish packages / lmcp-any (push) Successful in 4s
build and publish packages / lmcp-debian (push) Successful in 4s
build and publish packages / claude-his-any (push) Successful in 5s
build and publish packages / aish-any (push) Successful in 5s
build and publish packages / ffmpeg-v4l2-request-aarch64 (push) Successful in 5s
build and publish packages / claude-his-debian (push) Successful in 5s
build and publish packages / aish-debian (push) Successful in 5s
build and publish packages / libva-v4l2-request-fourier-aarch64 (push) Successful in 5s
build and publish packages / mpv-fourier-aarch64 (push) Successful in 5s
build and publish packages / ffmpeg-v4l2-request-debian (push) Has been cancelled
build and publish packages / libva-v4l2-request-fourier-debian (push) Has been cancelled
build and publish packages / mpv-fourier-debian (push) Has been cancelled
build and publish packages / daedalus-v4l2-debian (push) Has been cancelled
build and publish packages / daedalus-v4l2-dkms-debian (push) Has been cancelled
GCC 16.1.1 fixed the arm_neon.h #pragma target + SCS interaction. The cumulative patch already had a CFLAGS_xor-neon.o workaround. Verified on boltzmann with GCC 16.1.1 (test build exit code 0). Closes #20
49 lines
2.4 KiB
Markdown
49 lines
2.4 KiB
Markdown
# 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 |
|
||
|--------|------------|-------------------------------------------------|
|
||
| 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 |
|
||
| 5 | 2026-05-18 | SCS workaround deployed, pkgrel bump for rebuild |
|
||
| 6 | 2026-07-10 | Re-enable `CONFIG_SHADOW_CALL_STACK=y` — GCC 16.1.1 fixed the `arm_neon.h` `#pragma target` + SCS interaction |
|
||
|
||
## Known caveats
|
||
|
||
- 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.
|