README + danctnix-besser-pkgbuild/README: point at kernel-agent pkgrel=4 flow #21
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: marfrit/besser#21
Reference in New Issue
Block a user
Delete Branch "noether/readme-pkgrel4-kernel-agent-flow"
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?
Updates the gitea tl;dr to reflect the new home
Closing the third deliverable of the ohm migration goal: README tl;dr now points at the kernel-agent-managed pkgrel=4 flow.
Top-level README
Adds two new rows to the Repos table:
marfrit/marfrit-packages/arch/linux-pinetab2-danctnix-besser/— kernel-agent-driven PKGBUILD home (pkgrel=4+)marfrit/kernel-agent— manifest + per-patch series +ka-promote ohmbuildMarks the hand-managed pkgbuild dir as historical.
danctnix-besser-pkgbuild/README.mdbd42cd39106298879eeb…).BEB625FA7443171EA8D55F7carries forward unchanged because pkgrel=4's source is byte-identical to pkgrel=3.References
Build (PID 558898 on boltzmann) failed at bes2600_btuart.c:81: error: implicit declaration of function 'bes2600_chrdev_switch_subsys_glb' Root cause: the original danctnix-flavor adaptation overlaid Mobian's heavily-trimmed bes_chardev.{c,h} on top of pristine danctnix. Mobian's flavor (694 lines) had stripped out the BT/WiFi subsystem-switch orchestration that pristine danctnix (1387 lines) carries and that danctnix-only bes2600_btuart.c calls. Fix: restore pristine danctnix bes_chardev.{c,h} as the baseline for those two files in the danctnix flavor, then reapply Mobian's campaign-relevant changes: - Patch G: SPDX-License-Identifier header + corrected attribution - Patch B: bes2600_chrdev_do_bus_reset + _trigger_bus_reset (definitions in bes_chardev.c, declarations in bes_chardev.h, EXPORT_SYMBOL_GPL on _trigger_bus_reset since it is called from sta.c connection-loss-storm fast-recover path) Phase 6 thread-safety contract: bus_reset functions read bes2600_cdev.{sbus_ops,sbus_priv} without locking, identical to the Mobian-flavor source-of-truth - acceptable given the bus_reset is invoked from already-serialized higher-level error paths in sta.c. 48 files unchanged in count, +1412/-1243 (was +1426/-2003). The delta vs the previous patch is concentrated in bes_chardev.{c,h}: +776/-16 in .c (restoring the BT/WiFi switching infrastructure plus appending Patch B), +2/-2 in .h (declarations + SPDX). Patch verified to apply cleanly to v7.0-danctnix1 baseline. b2sum updated in PKGBUILD. Build retrigger pending on his. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>(1) Add `provides=("linux-pinetab2=$pkgver-$pkgrel")` and `conflicts=(linux-pinetab2)` so pacman -U cleanly replaces the upstream linux-pinetab2 package without needing --overwrite for the shared rk3566-pinetab2-*.dtb files. Verified end-to-end on ohm 2026-05-08: with these declarations pacman would refuse coexistence (matching the actual filesystem reality - both packages own the same DTB paths) and accept upgrade when removing the old package. Keeping `replaces=(wireguard-arch)` from upstream linux-pinetab2. Not adding linux-pinetab2 to replaces= since the soft-upstream intent is opt-in sidegrade, not auto-install on -Syu. (2) Replace the bash for-loop DTB strip with find -delete. The original loop silently no-op'd during the makepkg-fakeroot package() phase: build verification of the published .pkg.tar.zst showed 236 DTBs, 234 of them unrelated boards (px30-*, rk3308-*, rk3328-*, rk3399-*, etc). Root cause not pinned down (suspected nullglob or cwd interaction), but find -mindepth 1 -maxdepth 1 ! -name 'rk3566-pinetab2-*' -delete is robust to that environment and correctly identifies 2 to keep / 234 to remove on the existing pkgdir. Net pkg size impact: ~5 MB reduction (most non-pinetab2 DTBs are 20-40 KB). No kernel rebuild required - PKGBUILD-only metadata + package() logic change. Will take effect on the next makepkg run. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>Two readiness gaps surfaced after the end-to-end install verification on ohm 2026-05-08: (1) The "Building" section was a one-liner ("makepkg -s ... pacman -U ... reboot") with no actual install commands. Replaced with proper Building / Installing / Verifying / Rolling back sections, using the exact commands that worked end-to-end on ohm: - sudo pacman -U <pkg.tar.zst> - The new conflicts/provides metadata means no --overwrite needed - PineTab2 U-Boot script update via /boot/boot.txt + mkscr - Off-device backup (boot.scr.pre-besser) for trivial rollback - Post-reboot checks: uname -r, lsmod, /sys/module/bes2600/srcversion (2) The "What's in the patchset" table listed Patch G / Patch B / etc. without linking to the actual commits. Added a preamble pointer to the cleanups branch on marfrit/bes2600-dkms gitea, which is the source-of-truth for individual commits + Phase-7 verification logs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>