marfrit/kernel-agent
1
0
Fork 1
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

Migrate besser/patches/ into driver/bes2600/ scope-tagged tree #2

New Issue
Closed
opened 2026-05-09 08:56:17 +00:00 by marfrit · 0 comments
marfrit commented 2026-05-09 08:56:17 +00:00
Owner
Copy Link
Copy Source

Source

marfrit/besser/patches/ — ~30 BES2600 mainlining patch series, each in its own subdir, paired with -danctnix siblings (per-distro variants).

Example series content (staging-prep-series/): cover letter + 7 numbered patches.

Target

patches/driver/bes2600/<series-name>/ in marfrit/kernel-agent. Each series promotion-eligible independently per scope tag driver:bes2600.

Considerations

  • -danctnix siblings: keep both as separate series, or consolidate into one with target-conditional patches? DanctNIX-specific variants exist because vanilla series didn't apply on DanctNIX kernel base. Probably keep separate until BES2600 lands upstream, then collapse.
  • Promote target: ohm (PineTab2) initially. Future PineTab2 buyers benefit automatically via driver:bes2600 scope.
  • Coordination with bes2600-dkms (mobian fork): once besser series lands in mainline, bes2600-dkms package gets dropped from ohm. Mark this transition in manifest with a 'replaces dkms' note.

Acceptance

  • All series present under driver/bes2600/
  • Promotion eligibility per series (some are review-ready, some are early WIP)
  • Manifest for ohm references driver:bes2600 scope
  • DKMS-to-in-tree transition path documented

References

  • Memory: project_besser (umbrella for BES2600 mainlining)
  • README → 'Open follow-ups'
## Source `marfrit/besser/patches/` — ~30 BES2600 mainlining patch series, each in its own subdir, paired with `-danctnix` siblings (per-distro variants). Example series content (`staging-prep-series/`): cover letter + 7 numbered patches. ## Target `patches/driver/bes2600/<series-name>/` in marfrit/kernel-agent. Each series promotion-eligible independently per scope tag `driver:bes2600`. ## Considerations - `-danctnix` siblings: keep both as separate series, or consolidate into one with target-conditional patches? DanctNIX-specific variants exist because vanilla series didn't apply on DanctNIX kernel base. Probably keep separate until BES2600 lands upstream, then collapse. - Promote target: ohm (PineTab2) initially. Future PineTab2 buyers benefit automatically via `driver:bes2600` scope. - Coordination with `bes2600-dkms` (mobian fork): once besser series lands in mainline, bes2600-dkms package gets dropped from ohm. Mark this transition in manifest with a 'replaces dkms' note. ## Acceptance - [ ] All series present under `driver/bes2600/` - [ ] Promotion eligibility per series (some are review-ready, some are early WIP) - [ ] Manifest for ohm references `driver:bes2600` scope - [ ] DKMS-to-in-tree transition path documented ## References - Memory: `project_besser` (umbrella for BES2600 mainlining) - README → 'Open follow-ups'
marfrit added the area:patch-treemigration labels 2026-05-09 09:05:54 +00:00
marfrit added this to the rollout milestone 2026-05-09 09:05:54 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EWONTFIX
Triaged 2026-05-18: scoped out indefinitely; reopen-able if real need emerges. (HEVC-on-ampere first batch.)
 area:boltzmann
Touches boltzmann host
 area:fresnel
Touches fresnel host
 area:patch-tree
Touches the scope-tagged patches/ tree
 decision
Pending decision required (no clear default)
 migration
Bootstrap-time migration from existing trees into kernel-agent layout
No Label area:patch-tree migration
Milestone
No items
No Milestone rollout
Projects
Clear projects
No project
Assignees
Clear assignees
claude-ampere (Claude (ampere)) claude-boltzmann (Claude (boltzmann)) claude-noether (Claude (noether)) marfrit (Markus Fritsche)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: marfrit/kernel-agent#2
Delete Branch "%!s()"

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?