test0r
43c8f0cba8
Updates both flavors with the n_channels > 1 refinement (was > 0). The original guard refused ALL 5 GHz scans which broke 5 GHz association via NM band=a profiles (NM iterates freq_list per channel, single-channel scans were also refused). Tightened: only multi-channel 5 GHz scans (the per-band-sweep that triggers the firmware storm) are refused; single-channel 5 GHz scans pass through so NM/wpa_supplicant can find and associate to 5 GHz BSSes. Verified on ohm with locally-built pkgrel=3 (srcversion BEB625FA7443171EA8D55F7): associated to 5 GHz BSSID c0:25:06:e6:5b:33 on 5240 MHz / ch.48, 150 Mbit/s MCS 7 40MHz short-GI; Pattern A still 0 since boot. Patch file is now a concatenation of two commits from marfrit/bes2600-dkms bes2600/scan-filter-5ghz branch: 093a503 (original Patch I) 8cd10f4 (this refinement) patch -Np1 applies them sequentially -> net effect = single squash. Refs: besser#1 (closed), PKGBUILD update at marfrit/besser claude-noether-14 commit 122582e (pkgrel=3 deployed to ohm on 2026-05-18 same session).
patches/driver/bes2600/
BES2600 WiFi driver patches (drivers/staging/bes2600/*, mainline-bound).
Mirrored from marfrit/besser/patches/ on 2026-05-16.
Scope tag: driver:bes2600 (see fleet/ohm.yaml for the consumer).
Consumer: ohm (PineTab2, RK3566 + BES2600 SDIO).
Series taxonomy
30 series (15 base + 15 -danctnix siblings). The -danctnix
variants exist because vanilla series don't apply on the DanctNIX
kernel base (slightly different in-tree state for drivers/staging/bes2600/*).
Keep both as separate series until BES2600 lands upstream, then
collapse — issue #2 acceptance criterion.
Each series directory contains numbered .patch files plus
optionally a 0000-cover-letter.patch for multi-patch series.
Promotion eligibility (per series)
Marked here for the kernel-agent CLI (ka-promote) to pick up.
Markus to update as series mature. Default UNSET means "ask before
including in a build".
| Series | promote_eligible | Notes |
|---|---|---|
debian-copyright-fsf-address |
unset | Debian packaging metadata; not kernel-side |
drop-dpd-file-paths |
unset | |
drop-dpd-file-paths-danctnix |
unset | DanctNIX sibling |
drop-orphan-file-io |
unset | |
drop-orphan-file-io-danctnix |
unset | DanctNIX sibling |
enable-testmode |
unset | |
factory-drop-kernel-write |
unset | |
factory-drop-kernel-write-danctnix |
unset | DanctNIX sibling |
factory-series |
unset | |
factory-thread-dev |
unset | |
lmac-recover-via-mmc-hw-reset |
unset | |
lmac-recover-via-mmc-hw-reset-danctnix |
unset | DanctNIX sibling |
pm-detect-firmware-unsupported |
unset | |
pm-detect-firmware-unsupported-danctnix |
unset | DanctNIX sibling |
pm-gate-on-handshake |
unset | |
pm-state-resync |
unset | |
pm-state-resync-danctnix |
unset | DanctNIX sibling |
pm-timeout-silence |
unset | |
pm-timeout-silence-danctnix |
unset | DanctNIX sibling |
pm-wake-consume-state |
unset | |
pm-wake-consume-state-danctnix |
unset | DanctNIX sibling |
remove-chardev-user-interface |
unset | Cross-ref bes_chardev merge regression (besser #17) |
scan-defer-backoff-tune |
unset | |
scan-defer-backoff-tune-danctnix |
unset | DanctNIX sibling |
scan-defer-on-reject |
unset | |
scan-defer-on-reject-danctnix |
unset | DanctNIX sibling |
staging-prep-series |
unset | 7-patch cover-letter series; upstream-staging-prep work |
staging-prep-series-danctnix |
unset | DanctNIX sibling |
tx-sdio-dma-oob |
unset | |
tx-sdio-dma-oob-danctnix |
unset | DanctNIX sibling |
DKMS-to-in-tree transition path
bes2600-dkms (Mobian fork, in marfrit/bes2600-dkms) is the
out-of-tree shim that ohm currently uses for the BES2600 wifi+BT.
Once these driver/bes2600/ series land in mainline (or at least in
DanctNIX's PineTab2 kernel base):
- ohm's manifest drops the
bes2600-dkmspackage dependency kernel-agentbuilds the in-tree variant via the series listed heremarfrit/bes2600-dkmsrepo gets archived (kept as history)- PineTab2 buyers from then on get bes2600 directly out of the kernel
Track the dropdown in fleet/ohm.yaml (replaces_dkms: bes2600-dkms
once the cumulative series is enough to replace it).
Cumulative-patch generation order
The current single-patch cumulative (0001-bes2600-besser-cumulative-series.patch
in the existing PKGBUILD) is generated in this order on boltzmann:
A, B, C v3, F, G, D, E, C2, c5.x, c6.x, c7, H
This is NOT alphabetical — C2 follows E rather than coming after
C v3. ka-promote MUST honor an explicit series-ordering field
when concatenating, not sort by series name. Field name TBD; suggest
adding apply_order: to fleet/ohm.yaml (issue #5 will surface this
when the cumulative gets regenerated).
References
- Issue:
git.reauktion.de/marfrit/kernel-agent/issues/2 - Source repo:
git.reauktion.de/marfrit/besser/patches/ - Consumer: ohm (
fleet/ohm.yaml) - Related:
bes2600-dkms,linux-pinetab2-danctnix-besserPKGBUILD