Decide: boltzmann custom-kernel target (Neutron) or stay stock-BredOS? #4

New Issue

2026-05-09T08:56:18Z

marfrit commented

2026-05-09 08:56:18 +00:00

Status today

boltzmann runs BredOS stock kernel (Arch Linux ARM derivative for Rockchip). Volta umbrella exists (marfrit/volta README-only). Neutron subproject (project_neutron.md in memory) referenced as 'mainline / vendor kernel work for Rock 5 ITX+, UEFI-booted' — but no kernel patches exist in any repo yet.

Question for kernel-agent rollout

Does boltzmann enter the kernel-agent fleet as a customized target, or stay stock-BredOS? Three shapes:

(α) Stay stock. boltzmann is a workhorse, BredOS works, no urgent need. Defer Neutron indefinitely. Removes one target from kernel-agent's day-1 scope.

(β) Match ampere's level. Custom kernel package, mainline-or-near-mainline base, deliberate patch set. Real Neutron work. Significant scope expansion.

(γ) Selective patches only. Stay on BredOS kernel base, but apply a small set of in-tree patches that benefit boltzmann (e.g., 0009 btrtl from genbook scope-shared). Lightweight Neutron — adds boltzmann to scope-tagged manifest but minimal divergence from BredOS.

Considerations

boltzmann is always-on infra (kernel-build host kbuild-aarch64, Open WebUI, hossenfelder LLM proxy). A bad kernel update has fleet impact.
edk2-rk3588 UEFI boot path is different from ampere's u-boot path — Quark subproject territory.
(γ) is the cheapest way to start using kernel-agent against boltzmann without a full Neutron commitment.

Recommendation

(γ) as a starting point. Pull in scope-shared patches (driver/btrtl, soc/rockchip/rk3588 items where they apply) without forking the kernel base. Graduate to (β) if/when there's a concrete reason (e.g., a feature only in mainline).

Acceptance

Decision made (α / β / γ)
If (β) or (γ): fleet/boltzmann.yaml manifest exists and declares scope-tag set
If (α): fleet/boltzmann.yaml does NOT exist (per hard rule, no manifest = not a target)

References

Memory: project_neutron.md, project_volta.md
README → 'Targets' (boltzmann currently listed as 'customized today' — this is aspirational, reality TBD per this issue)

## Status today boltzmann runs BredOS stock kernel (Arch Linux ARM derivative for Rockchip). Volta umbrella exists (`marfrit/volta` README-only). Neutron subproject (`project_neutron.md` in memory) referenced as 'mainline / vendor kernel work for Rock 5 ITX+, UEFI-booted' — but no kernel patches exist in any repo yet. ## Question for kernel-agent rollout Does boltzmann enter the kernel-agent fleet as a customized target, or stay stock-BredOS? Three shapes: (α) **Stay stock.** boltzmann is a workhorse, BredOS works, no urgent need. Defer Neutron indefinitely. Removes one target from kernel-agent's day-1 scope. (β) **Match ampere's level.** Custom kernel package, mainline-or-near-mainline base, deliberate patch set. Real Neutron work. Significant scope expansion. (γ) **Selective patches only.** Stay on BredOS kernel base, but apply a small set of in-tree patches that benefit boltzmann (e.g., 0009 btrtl from genbook scope-shared). Lightweight Neutron — adds boltzmann to scope-tagged manifest but minimal divergence from BredOS. ## Considerations - boltzmann is always-on infra (kernel-build host kbuild-aarch64, Open WebUI, hossenfelder LLM proxy). A bad kernel update has fleet impact. - edk2-rk3588 UEFI boot path is different from ampere's u-boot path — Quark subproject territory. - (γ) is the cheapest way to start using kernel-agent against boltzmann without a full Neutron commitment. ## Recommendation (γ) as a starting point. Pull in scope-shared patches (`driver/btrtl`, `soc/rockchip/rk3588` items where they apply) without forking the kernel base. Graduate to (β) if/when there's a concrete reason (e.g., a feature only in mainline). ## Acceptance - [ ] Decision made (α / β / γ) - [ ] If (β) or (γ): `fleet/boltzmann.yaml` manifest exists and declares scope-tag set - [ ] If (α): `fleet/boltzmann.yaml` does NOT exist (per hard rule, no manifest = not a target) ## References - Memory: `project_neutron.md`, `project_volta.md` - README → 'Targets' (boltzmann currently listed as 'customized today' — this is aspirational, reality TBD per this issue)

marfrit added the area:boltzmann decision labels 2026-05-09 09:05:55 +00:00

marfrit added this to the rollout milestone 2026-05-09 09:05:55 +00:00

claude-noether referenced this issue

2026-05-15 15:32:29 +00:00

phase 1: promote vb2_dma_resv RFC v2 + add ka-status + ampere as 2nd aarch64 host #7

marfrit referenced this issue

2026-05-18 08:08:22 +00:00

[ka:cli-build-out] ka-promote: resolve manifest + concat scope-tagged series into cumulative patch #22

marfrit referenced this issue

2026-05-18 08:21:24 +00:00

[ka:cli-build-out] ka-promote: resolve manifest + concat scope-tagged series into cumulative patch #22

marfrit referenced this issue from a commit