vasilito/RedBear-OS
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

docs: resolve stale cross-references after 2026-07-27 doc consolidation

Browse Source 
The 2026-07-27 Round 9 cleanup deleted 36 docs (3D-DRIVER-PLAN,
WAYLAND-IMPLEMENTATION-PLAN, DRM-MODERNIZATION-EXECUTION-PLAN,
REDBEAR-FULL-SDDM-BRINGUP, and the entire archived/ and
legacy-obsolete-2026-07-25/ contents) but several active docs still
cross-referenced those deleted files. This commit sweeps the surviving
docs and:

* Replaces every deleted-path reference with the live target:

    WAYLAND-IMPLEMENTATION-PLAN.md         -> 3D-DESKTOP-COMPREHENSIVE-PLAN.md
    3D-DRIVER-PLAN.md                      -> 3D-DESKTOP-COMPREHENSIVE-PLAN.md
    REDBEAR-FULL-SDDM-BRINGUP.md           -> 3D-DESKTOP-COMPREHENSIVE-PLAN.md
    legacy-obsolete-2026-07-25/DRM...      -> 3D-DESKTOP-COMPREHENSIVE-PLAN.md
    legacy-obsolete-2026-07-25/IRQ...      -> IRQ-AND-LOWLEVEL-...-PLAN.md
    archived/UPSTREAM-SYNC-PROCEDURE.md    -> removed (sync procedure now in
                                              BUILD-CACHE-PLAN.md +
                                              sync-versions.sh)
    archived/RELIBC-IPC-ASSESSMENT-...     -> removed (work captured in
                                              KERNEL-IPC-CREDENTIAL-PLAN.md)
    archived/DRIVER-MANAGER-MIGRATION-PLAN -> removed (history in DRIVER-MANAGER.md
                                              and git log)
    archived/INTEL-HDA-IMPLEMENTATION-PLAN -> removed (track now in 3D-DESKTOP-
                                              COMPREHENSIVE-PLAN.md § SOF/AVS)

* Rewrites pcid-spawner references to driver-manager in PACKAGE-BUILD-QUIRKS,
  PATCH-GOVERNANCE, NETWORKING-IMPROVEMENT, LG-GRAM-16Z90TP, and the IRQ plan
  status note. The retired pcid-spawner service no longer exists in any
  redbear-* config as of the 2026-07-24 cutover.

* Rewrites CONSOLE-TO-KDE-DESKTOP-PLAN.md §9 plan table to point at the
  post-Round-9 canonical doc map (3D-DESKTOP-COMPREHENSIVE-PLAN.md as the
  single coherent 3D-render plan; IRQ plan at top-level). Drops the
  misleading 'archived legacy-obsolete-2026-07-25/' status line and the
  'work subsumed by Round 1-5' sentence that was explicitly rejected by
  SUPERSEDED-DOC-LOG.

* Updates 3D-DESKTOP-COMPREHENSIVE-PLAN.md §10 to mark the REPLACE, RESTORE,
  and DELETE pre-execution audit as completed 2026-07-27. Tables remain as
  historical record of what was done, with a pointer to the backup tarballs
  and SUPERSEDED.md log.

* Bumps 'Last updated' of CONSOLE-TO-KDE-DESKTOP-PLAN.md to v6.1.

13 files changed, +78/-65.
This commit is contained in:
vasilito
2026-07-27 19:08:58 +09:00
parent c21c70912e
commit 163d6f0a59
13 changed files with 78 additions and 65 deletions
Download Patch File Download Diff File Expand all files Collapse all files
local/AGENTS.md
+9 -11
View File
@@ -1407,20 +1407,18 @@ When mainline updates affect our work:
## PLANNING NOTES
- `docs/07-RED-BEAR-OS-IMPLEMENTATION-PLAN.md` is the canonical public execution plan.
- `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` (v4.0) is the canonical comprehensive plan —
- `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` is the canonical comprehensive plan —
supersedes all individual subsystem docs. See it for current state, blockers, and roadmap.
- `local/docs/WAYLAND-IMPLEMENTATION-PLAN.md` is the canonical Wayland subsystem plan beneath the
desktop path. Use it for Wayland-specific stability, completeness, ownership, and runtime-proof
sequencing.
- `local/docs/legacy-obsolete-2026-07-25/DRM-MODERNIZATION-EXECUTION-PLAN.md` and
`local/docs/legacy-obsolete-2026-07-25/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md`
were moved there during the Round 5 audit. The 3D render-path work they covered
is now consolidated in `local/docs/3D-DRIVER-PLAN.md` (Rounds 1-7). The current
DRM/KMS focus is the Mesa redox gallium winsys and the compositor's `redox-drm` scheme.
- `local/docs/3D-DESKTOP-COMPREHENSIVE-PLAN.md` is the canonical post-Round-9 plan that
consolidates the 3D render path, Wayland compositor stability, and DRM/KMS modernization
(formerly `3D-DRIVER-PLAN.md`, `WAYLAND-IMPLEMENTATION-PLAN.md`,
`DRM-MODERNIZATION-EXECUTION-PLAN.md`, and `REDBEAR-FULL-SDDM-BRINGUP.md`, all deleted
2026-07-27 — see `local/docs/legacy-obsolete-2026-07-25/SUPERSEDED.md` for the audit log).
The current DRM/KMS focus is the Mesa redox gallium winsys and the compositor's `redox-drm` scheme.
- The historical `local/docs/AMD-FIRST-INTEGRATION.md`, `local/docs/HARDWARE-3D-ASSESSMENT.md`,
and `local/docs/DMA-BUF-IMPROVEMENT-PLAN.md` were deleted (per CONSOLE-TO-KDE-DESKTOP-PLAN.md §10).
AMD and Intel machines are equal-priority Red Bear OS targets. The current canonical 3D driver
plan is `local/docs/3D-DRIVER-PLAN.md`; the canonical desktop path plan is
plan is `local/docs/3D-DESKTOP-COMPREHENSIVE-PLAN.md`; the canonical desktop path plan is
`local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md`.
- The earlier Phase 0–3 reassessment bridge has been retired. Its reconciliation role is now
covered by `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` and
@@ -1429,7 +1427,7 @@ When mainline updates affect our work:
including the bounded role of `linux-kpi` and the native wireless control-plane direction.
- `local/docs/USB-IMPLEMENTATION-PLAN.md` and `local/docs/BLUETOOTH-IMPLEMENTATION-PLAN.md` should
also be treated as first-class subsystem plans, not as side notes.
- `local/docs/legacy-obsolete-2026-07-25/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` is the current umbrella plan for
- `local/docs/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` is the current umbrella plan for
IRQ delivery, MSI/MSI-X quality, IOMMU validation, and other low-level controller completeness work.
- `local/docs/DRIVER-MANAGER.md` (consolidated 2026-07-27, post-v5.9 systematic assessment) is the canonical
current-state document for `driver-manager` (`local/recipes/system/driver-manager/`). The
local/docs/3D-DESKTOP-COMPREHENSIVE-PLAN.md
+21 -6
View File
@@ -958,20 +958,35 @@ gaps per §2 / §5 / §6 of this document.
`/tmp/opencode/stale-doc-backup-2026-07-27.tar.gz` per AGENTS.md "NEVER delete" rule and
this document's notepad policy (§0 binding policy).
### 10.1 REPLACE (this doc supersedes)
### 10.1 REPLACE — ✅ completed 2026-07-27
Both files listed below were deleted and their content absorbed here; backups are in
`/tmp/opencode/stale-doc-backup-2026-07-27.tar.gz` and
`/tmp/opencode/round2-stale-doc-backup-2026-07-27-round2.tar.gz`. The audit trail is in
`local/docs/legacy-obsolete-2026-07-25/SUPERSEDED.md`.
| Doc | Lines | Reason |
|-----|-------|--------|
| `local/docs/3D-DRIVER-PLAN.md` | 960 | All Round 1-7 work fact-of-record here; operating rule restated in §0 |
| `local/docs/REDBEAR-FULL-SDDM-BRINGUP.md` | 177 | Build-campaign log; status captured in §1.5 |
### 10.2 RESTORE (currently mis-archived)
### 10.2 RESTORE — ✅ completed 2026-07-27
| Doc | Lines | Action |
|-----|-------|--------|
| `local/docs/legacy-obsolete-2026-07-25/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` | 1,022 | **Move to top-level** `local/docs/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md`. Doc self-declares active authority (§0 of itself: *"despite the legacy folder name confusion, this file is still the active low-level-controller authority"*). Update stale `pcid-spawner` references to `driver-manager`. Update `local/docs/legacy-obsolete-2026-07-25/SUPERSEDED.md` to reflect. |
The IRQ plan restoration was completed; it now lives at the top-level
`local/docs/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md`. Stale
`pcid-spawner` references were updated to `driver-manager` in the same
pass (and again as part of this round's doc cleanup). See
`local/docs/legacy-obsolete-2026-07-25/SUPERSEDED.md` for the audit log.
### 10.3 DELETE candidates (with backup)
### 10.3 DELETE candidates — ✅ completed 2026-07-27
All 28 docs listed below (and the 6 boot-log/fork-push-status entries
that followed) were deleted in commit `092d1b39c3` ("docs: consolidate
3D-desktop docs"). A backup tarball of all deleted files is preserved at
`/tmp/opencode/stale-doc-backup-2026-07-27.tar.gz` (round 1) and
`/tmp/opencode/round2-stale-doc-backup-2026-07-27-round2.tar.gz`
(round 2). The audit trail lives in
`local/docs/legacy-obsolete-2026-07-25/SUPERSEDED.md`.
| Doc | Lines | Reason |
|-----|-------|--------|
local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md
+6 -9
View File
@@ -247,7 +247,7 @@ not in the patches list. Fix: add the missing patches to `recipes/libs/mesa/reci
> `-Dgallium-drivers=softpipe,llvmpipe,virgl` (no `iris`, no `crocus`, no `radeonsi`).
> The Mesa 26.1.4 source tree has no `redox` EGL platform at all. The Intel kernel
> backend supports only Gen9–Gen14 (no Lunar Lake, no Panther Lake). Full assessment
> and 7-phase execution plan: **`local/docs/3D-DRIVER-PLAN.md`** (2026-07-24).
> and 7-phase execution plan: **`local/docs/3D-DESKTOP-COMPREHENSIVE-PLAN.md`** (2026-07-27).
**QEMU test gap**: The QEMU test script uses `-device virtio-gpu` (2D-only KMS) instead of
`-device virtio-vga-gl` (3D virgl-capable). The redox-drm virtio-gpu backend fully supports
@@ -2108,14 +2108,11 @@ This document is the authority. Subsystem plans remain for deep-dive detail:
| Plan | Covers |
|------|--------|
| `KERNEL-IPC-CREDENTIAL-PLAN.md` | Kernel credential syscalls, IPC, RLIMIT — Phases K1-K2,K4 complete |
| `IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` *(archived `legacy-obsolete-2026-07-25/`)* | PCI/IRQ/MSI-X/IOMMU quality — work subsumed by Round 1–5 base/kernel work |
| `IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` | PCI/IRQ/MSI-X/IOMMU quality — canonical low-level controller authority |
| `ACPI-IMPROVEMENT-PLAN.md` | ACPI shutdown, power, sleep states |
| `archived/RELIBC-IPC-ASSESSMENT-AND-IMPROVEMENT-PLAN.md` | relibc IPC surface |
| `DRM-MODERNIZATION-EXECUTION-PLAN.md` *(archived `legacy-obsolete-2026-07-25/`)* | DRM/KMS modernization — render-path work subsumed by `3D-DRIVER-PLAN.md` Rounds 1–7 |
| `WAYLAND-IMPLEMENTATION-PLAN.md` | Wayland compositor stability — diagnostic content current; status table superseded by `3D-DRIVER-PLAN.md` Rounds 1–7 |
| `DBUS-INTEGRATION-PLAN.md` | D-Bus architecture |
| `GREETER-LOGIN-IMPLEMENTATION-PLAN.md` | Greeter/login design |
| `3D-DRIVER-PLAN.md` *(canonical)* | Mesa + virgl + Intel iris + AMD radeonsi — single coherent post-Round-7 plan |
| `3D-DESKTOP-COMPREHENSIVE-PLAN.md` *(canonical)* | Mesa + virgl + Intel iris + AMD radeonsi — single coherent post-Round-9 plan; supersedes the old 3D-DRIVER-PLAN, WAYLAND-IMPLEMENTATION-PLAN, DRM-MODERNIZATION-EXECUTION-PLAN, and REDBEAR-FULL-SDDM-BRINGUP |
---
@@ -2139,7 +2136,7 @@ This document is the authority. Subsystem plans remain for deep-dive detail:
---
**Last updated:** 2026-07-27 (v6.0)
**Last updated:** 2026-07-27 (v6.1 — Round 9 doc consolidation: removed stale references to deleted docs, updated plan table to post-Round-9 state)
**Canonical source:** `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md`
**Cited by:** `README.md`, `AGENTS.md`, `local/AGENTS.md`, `DBUS-INTEGRATION-PLAN.md`, `3D-DRIVER-PLAN.md`, `REDBEAR-FULL-SDDM-BRINGUP.md`, `GREETER-LOGIN-IMPLEMENTATION-PLAN.md`
**Supersedes:** `COMPREHENSIVE-OS-ASSESSMENT.md`, `DESKTOP-STACK-CURRENT-STATUS.md`, all layer-specific plans
**Cited by:** `README.md`, `AGENTS.md`, `local/AGENTS.md`, `DBUS-INTEGRATION-PLAN.md`, `GREETER-LOGIN-IMPLEMENTATION-PLAN.md`, `3D-DESKTOP-COMPREHENSIVE-PLAN.md`
**Supersedes:** `COMPREHENSIVE-OS-ASSESSMENT.md`, `DESKTOP-STACK-CURRENT-STATUS.md`, `3D-DRIVER-PLAN.md`, `REDBEAR-FULL-SDDM-BRINGUP.md`, all layer-specific plans
local/docs/DRIVER-MANAGER.md
+8 -5
View File
@@ -11,9 +11,11 @@ and the actionable fix/improvement plan.
**Cross-reference baseline:** Linux kernel 7.1 (`local/reference/linux-7.1/` at
`ab9de95c9`), CachyOS (`local/reference/cachyos/`).
> **Historical material:** the v1.0 → v5.9 migration plan is archived at
> `local/docs/archived/DRIVER-MANAGER-MIGRATION-PLAN.md`. Read this doc for
> current state; read the archive for the round-by-round history.
> **Historical material:** the v1.0 → v5.9 migration plan was archived at
> `local/docs/archived/DRIVER-MANAGER-MIGRATION-PLAN.md` (deleted 2026-07-27 —
> see `local/docs/legacy-obsolete-2026-07-25/SUPERSEDED.md` audit log).
> Round-by-round history lives in this document's "Per-fix summary" table and
> in the git history of `local/recipes/system/driver-manager/source/`.
---
@@ -871,8 +873,9 @@ referencing absent binaries per "honest absence" policy).
matrix (operator-only gate).
- `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` — desktop path plan v6.0,
records the cutover milestone.
- `local/docs/REDBEAR-FULL-SDDM-BRINGUP.md` — current SDDM bringup,
driver-manager as sole ISO blocker.
- `local/docs/3D-DESKTOP-COMPREHENSIVE-PLAN.md` § SDDM bringup — driver-manager
as sole ISO blocker (the legacy `REDBEAR-FULL-SDDM-BRINGUP.md` was
consolidated into it during the 2026-07-27 Round 9 doc cleanup).
- `local/docs/WIFI-IMPLEMENTATION-PLAN.md` — Wi-Fi subsystem plan.
- `local/docs/USB-IMPLEMENTATION-PLAN.md` — USB subsystem plan.
- `local/docs/QUIRKS-SYSTEM.md` — hardware quirks infrastructure.
local/docs/GREETER-LOGIN-IMPLEMENTATION-PLAN.md
+1 -1
View File
@@ -783,7 +783,7 @@ greeter/auth/session-boundary implementation inside this plan.
| `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` | Parent desktop-path authority; this plan fills the graphical login boundary beneath it |
| `local/docs/DBUS-INTEGRATION-PLAN.md` | Parent session/D-Bus authority for `redbear-sessiond` and related service model |
| `CONSOLE-TO-KDE-DESKTOP-PLAN.md` (§2) | Current build/boot status snapshot — superseded the deleted `DESKTOP-STACK-CURRENT-STATUS.md` |
| `local/docs/WAYLAND-IMPLEMENTATION-PLAN.md` | Wayland/compositor subsystem plan beneath the desktop path |
| `local/docs/3D-DESKTOP-COMPREHENSIVE-PLAN.md` | Wayland/compositor subsystem plan beneath the desktop path (the legacy `WAYLAND-IMPLEMENTATION-PLAN.md` was consolidated into it during the 2026-07-27 Round 9 doc cleanup) |
| `docs/07-RED-BEAR-OS-IMPLEMENTATION-PLAN.md` | Repo-wide product/profile/workstream framing |
This document does **not** replace any of the above. It fills a missing subsystem-planning gap:
local/docs/HARDWARE-VALIDATION-MATRIX.md
+1 -1
View File
@@ -81,7 +81,7 @@ this validation matrix.
- The login-based QEMU proofs (PS/2 + serio, monotonic timer, IOMMU first-use, USB storage BOT)
now run through `local/scripts/qemu-login-expect.py` (stdlib python) instead of the host
`expect` tool — no external dependency, per-step timeouts, and safe retry on premature QEMU
death. See `local/docs/legacy-obsolete-2026-07-25/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` § "Runtime proof
death. See `local/docs/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` § "Runtime proof
status (2026-07-20)".
- MSI-X (virtio-net) and xHCI interrupt-driven mode were re-confirmed on the current
`redbear-mini` ISO — once more on 2026-07-20 ~09:10 JST via `test-lowlevel-controllers-qemu.sh`
local/docs/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md
+7 -6
View File
@@ -1,11 +1,12 @@
# Red Bear OS IRQ and Low-Level Controllers Enhancement Plan
> **Status note (2026-07-26):** despite the legacy folder name confusion, this file is still the
> active low-level-controller authority for IRQ/MSI/MSI-X/IOMMU runtime-proof sequencing. But its
> old `pcid-spawner` Wave 1 tasks are no longer live: `pcid-spawner` was retired/removed in the
> driver-manager cutover (v5.0, 2026-07-24), and those responsibilities now live in
> `local/docs/DRIVER-MANAGER.md` (current state) / `local/docs/archived/DRIVER-MANAGER-MIGRATION-PLAN.md`
> (round-by-round history).
> **Status note (2026-07-27):** this file is still the active low-level-controller authority
> for IRQ/MSI/MSI-X/IOMMU runtime-proof sequencing. Its old `pcid-spawner` Wave 1 tasks are no
> longer live: `pcid-spawner` was retired/removed in the driver-manager cutover (v5.0, 2026-07-24),
> and those responsibilities now live in `local/docs/DRIVER-MANAGER.md` (current state). The
> archived `local/docs/archived/DRIVER-MANAGER-MIGRATION-PLAN.md` was deleted 2026-07-27 as part
> of the Round 9 doc cleanup; see `local/docs/legacy-obsolete-2026-07-25/SUPERSEDED.md` for the
> audit log. Round-by-round history remains accessible via `git log` on `local/recipes/system/driver-manager/source/`.
## Purpose
local/docs/KERNEL-IPC-CREDENTIAL-PLAN.md
+2 -5
View File
@@ -17,7 +17,6 @@ kernel guidance in other docs.
|----------|-------------|
| `CONSOLE-TO-KDE-DESKTOP-PLAN.md` | Parent: CONSOLE-TO-KDE v5.9 (2026-07-21; Kernel & Core Infrastructure) |
| `IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` | Sibling: IRQ/PCI/MSI-X — not duplicated here |
| `archived/RELIBC-IPC-ASSESSMENT-AND-IMPROVEMENT-PLAN.md` | Companion: relibc IPC surface — this plan covers kernel side |
| `ACPI-IMPROVEMENT-PLAN.md` | Sibling: ACPI power/shutdown — relevant for §4 (shutdown robustness) |
| `CONSOLE-TO-KDE-DESKTOP-PLAN.md` | Consumer: desktop stack depends on kernel work here |
@@ -546,7 +545,6 @@ Current state: all three are recipe-applied patches. Goal: upstream into relibc
- Monitor upstream relibc for equivalent implementations
- When upstream absorbs: shrink/drop Red Bear patch chain
- When upstream does NOT absorb after 3+ months: promote to durable Red Bear-maintained
- See `local/docs/archived/RELIBC-IPC-ASSESSMENT-AND-IMPROVEMENT-PLAN.md` Phase I5
### Phase K4: Resource Limits and Process Management (Week 4-6)
@@ -662,7 +660,7 @@ Phase K4 (limits/ptrace) ──────────────────
|------|---------------|--------|
| IRQ / MSI-X / IOMMU | `IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` | Waves 1-6 complete, hardware validation open |
| ACPI shutdown / power | `ACPI-IMPROVEMENT-PLAN.md` | Waves 1-2 complete, sleep states deferred |
| relibc IPC surface | `archived/RELIBC-IPC-ASSESSMENT-AND-IMPROVEMENT-PLAN.md` | Phases I1-I5, message queues deferred |
| relibc IPC surface | (this plan; the standalone `archived/RELIBC-IPC-ASSESSMENT-AND-IMPROVEMENT-PLAN.md` was deleted 2026-07-27 — see `local/docs/legacy-obsolete-2026-07-25/SUPERSEDED.md`) | Phases I1-I5, message queues deferred |
| D-Bus / sessiond | `DBUS-INTEGRATION-PLAN.md` | Phase 1 complete, Phase 2 in progress |
| Greeter / login | `GREETER-LOGIN-IMPLEMENTATION-PLAN.md` | Active, bounded proof passing |
| Desktop path | `CONSOLE-TO-KDE-DESKTOP-PLAN.md` | Phase 1-5 model, KWin building |
@@ -740,8 +738,7 @@ local/scripts/test-credential-syscalls-guest.sh # In-guest checker
- `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` — Canonical comprehensive plan
- `docs/01-REDOX-ARCHITECTURE.md` — Architecture reference
- `local/docs/legacy-obsolete-2026-07-25/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` — IRQ/PCI plan (sibling)
- `local/docs/archived/RELIBC-IPC-ASSESSMENT-AND-IMPROVEMENT-PLAN.md` — IPC surface plan (companion)
- `local/docs/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` — IRQ/PCI plan (sibling)
- `local/docs/ACPI-IMPROVEMENT-PLAN.md` — ACPI/shutdown plan (sibling)
- `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` — Desktop path plan (consumer)
- `recipes/core/kernel/source/src/syscall/mod.rs` — Syscall dispatch (primary implementation target)
local/docs/LG-GRAM-16Z90TP-COMPATIBILITY-PLAN.md
+5 -4
View File
@@ -126,7 +126,8 @@ Reviewed `local/sources/base/drivers/pcid/src/main.rs` (411 lines):
- **Device enable**: bus mastering + memory + IO enable. MSI/MSI-X disabled before re-enable.
- **IRQ routing**: legacy IRQ via device-tree-style `interrupt_map` with pin/line mapping.
- **Wiring**: registers `/scheme/pci` via `register_sync_scheme`. Registers with acpid via
`/scheme/acpi/register_pci` for ACPI integration. pcid-spawner spawns drivers on detection.
`/scheme/acpi/register_pci` for ACPI integration. driver-manager spawns drivers on detection
(the legacy pcid-spawner was retired 2026-07-24 — see `local/docs/DRIVER-MANAGER.md`).
- **Known limitations** (documented FIXMEs, not bugs):
- Bus 0x80 hardcoded scan (should come from ACPI bus enumeration)
- MCFG only describes first host bridge (multi-CPU systems need ACPI enumeration)
@@ -140,7 +141,7 @@ UEFI 2.7 (Phoenix) → Red Bear bootloader (✅ expected)
→ kernel: x2APIC detect (✅), 16-core SMP (✅), MADT (✅), MCFG ECAM 0xC0000000 (✅)
→ initfs: pcid → nvmed (✅ SK Hynix) → rootfs mount (✅)
→ vesad + fbcond console (✅)
→ pcid-spawner + driver-manager:
→ driver-manager (post-cutover, the pcid-spawner step no longer runs):
xhcid ×2 (✅ class match, Intel baseline quirks — watch 7ec0)
ps2d (✅)
ihdad (🟡 probes, finds no usable codec — must fail gracefully, not hang)
@@ -255,7 +256,7 @@ thermal throttling engages and recovers under sustained load.
### PHASE 3 — Display: VESA → DRM/KMS on Meteor Lake (L, critical path for desktop)
Follows `local/docs/legacy-obsolete-2026-07-25/DRM-MODERNIZATION-EXECUTION-PLAN.md` Workstream C.
Follows `local/docs/3D-DESKTOP-COMPREHENSIVE-PLAN.md` (the legacy `DRM-MODERNIZATION-EXECUTION-PLAN.md` was consolidated into it during the 2026-07-27 Round 9 doc cleanup; see `local/docs/legacy-obsolete-2026-07-25/SUPERSEDED.md`).
| # | Work item | Files | Effort |
|---|---|---|---|
@@ -492,7 +493,7 @@ real wireless connectivity, not bounded simulation.
|---|---|---|---|
| 8.0 | Interim (do first): USB-audio dongle path via `redbear-usbaudiod` validated on host — documented as the interim answer | redbear-usbaudiod | S |
| 8.1 | Probe ihdad on 8086:7728 to record exact failure mode (expected: no codecs behind DSP); ensure graceful failure, never a boot hang | `ihdad/src/hda/device.rs` | S |
| 8.2 | **SOF/AVS port**: cAVS 2.5 (ARL) DSP bring-up — power gating, ROM boot, `sof-arl.ri` firmware download via firmware-loader, IPC4 channel, HDA link DMA. Reference: `local/reference/linux-7.1/sound/soc/sof/intel/` + `sound/soc/intel/avs/`; revive `local/docs/archived/INTEL-HDA-IMPLEMENTATION-PLAN.md` HDA-011 track | new `local/recipes/drivers/redbear-sof/` (per LINUX REFERENCE SOURCE POLICY: implemented in-tree, Linux as reference only) | XL |
| 8.2 | **SOF/AVS port**: cAVS 2.5 (ARL) DSP bring-up — power gating, ROM boot, `sof-arl.ri` firmware download via firmware-loader, IPC4 channel, HDA link DMA. Reference: `local/reference/linux-7.1/sound/soc/sof/intel/` + `sound/soc/intel/avs/`; HDA-011 track lives in `local/docs/3D-DESKTOP-COMPREHENSIVE-PLAN.md` § SOF/AVS section (the archived `INTEL-HDA-IMPLEMENTATION-PLAN.md` was deleted 2026-07-27) | new `local/recipes/drivers/redbear-sof/` (per LINUX REFERENCE SOURCE POLICY: implemented in-tree, Linux as reference only) | XL |
| 8.3 | ALC298 codec verbs over the HDA link; speaker + headphone jack routing; DMIC later | sof codec layer | L |
**Gate 8:** Speaker playback on the host. (DMIC + HDMI audio are post-gate follow-ups.)
local/docs/NETWORKING-IMPROVEMENT-PLAN.md
+2 -2
View File
@@ -310,7 +310,7 @@ All upstream commits have been verified present in local forks. Key commit statu
| libredox | `b99b204` (+rb0.3.1) | `bedf012` | 2 commits (fcntl function) |
All forks intentionally kept at `+rb0.3.1` with Red Bear-specific changes applied.
See `local/docs/archived/UPSTREAM-SYNC-PROCEDURE.md` for sync procedure.
Sync procedure lives in `local/docs/BUILD-CACHE-PLAN.md` and `local/scripts/sync-versions.sh`.
Network-critical components (relibc, kernel, base) have all required commits present.
---
@@ -923,7 +923,7 @@ Phase 0 (upstream sync, 2-3w) ──┬── Phase 1 (multi-NIC, capabilities,
| `config/redbear-wifi-experimental.toml` | Wi-Fi experimental target (includes `redbear-iwlwifi`). |
| `config/redbear-mini.toml` | Mini target: includes `redbear-netctl`, `redbear-netstat`, `redbear-wifictl`, `smolnetd` service. |
| `config/redbear-full.toml` | Full desktop target. |
| `/etc/init.d/10_smolnetd.service` | smolnetd (notify type). Requires `00_pcid-spawner`. |
| `/etc/init.d/10_smolnetd.service` | smolnetd (notify type). Requires `00_driver-manager` (post-cutover, the legacy `00_pcid-spawner` service no longer exists). |
| `/etc/init.d/10_dhcpd.service` | dhcpd (oneshot_async). Requires `10_smolnetd`. |
### Custom Red Bear Networking Tools (`local/recipes/system/`)
local/docs/PACKAGE-BUILD-QUIRKS.md
+10 -10
View File
@@ -1077,17 +1077,18 @@ When you encounter a new build quirk:
## Package: base-initfs (initfs image builder)
### pcid Must Start Before pcid-spawner
### pcid Must Start Before driver-manager
**Problem:** `pcid-spawner` calls `fs::read_dir("/scheme/pci")` as its first
action. `/scheme/pci` is created by `pcid` via `register_sync_scheme()`. If
`pcid` is not started, `pcid-spawner` fails with `ENODEV`.
**Problem:** `driver-manager` (the replacement for the retired `pcid-spawner`,
see `local/docs/DRIVER-MANAGER.md` § "Cutover history") calls
`fs::read_dir("/scheme/pci")` as its first action. `/scheme/pci` is created
by `pcid` via `register_sync_scheme()`. If `pcid` is not started, the driver
match/claim loop fails with `ENODEV`.
**Root cause:** No init service started `pcid` in initfs. The upstream model
**Root cause:** No init service started `pcid` in initfs. The historical model
assumed `pcid` would be started, but no `.service` file existed for it. This
was masked in 0.2.3 because `driver-manager` (Red Bear's replacement) does
its own PCI enumeration via `redox_driver_pci` and doesn't depend on
`/scheme/pci`.
was masked in 0.2.3 because `driver-manager` does its own PCI enumeration via
`redox_driver_pci` and doesn't depend on `/scheme/pci`.
**Fix:** Added `35_pcid.service` to `init.initfs.d/`:
```ini
@@ -1101,7 +1102,7 @@ type = { scheme = "pci" }
```
The `type = { scheme = "pci" }` tells init to wait for `/scheme/pci` to be
registered before marking the service as started. This ensures `pcid-spawner`
registered before marking the service as started. This ensures `driver-manager`
(which depends on `35_pcid.service` via `requires_weak`) only runs after
`/scheme/pci` exists.
@@ -1172,7 +1173,6 @@ fn kcall(&self, fds: &[usize], payload: UserSliceRw, flags: CallFlags,
| Document | Relevance |
|----------|-----------|
| `local/docs/archived/UPSTREAM-SYNC-PROCEDURE.md` | Per-package sync notes include build quirks |
| `AGENTS.md` | Project-level build commands and conventions |
| `local/AGENTS.md` | Local fork model, recipe structure |
| `src/cook/script.rs` | `DYNAMIC_INIT`, `reexport_flags`, `cookbook_cmake` definitions |
local/docs/PATCH-GOVERNANCE.md
+3 -2
View File
@@ -47,8 +47,9 @@ Some patches have interdependencies:
- `P2-acpi-i2c-resources.patch` must apply before `P2-daemon-hardening.patch`
(workspace entries reference source files created by the former)
- `P2-boot-runtime-fixes.patch` modifies hwd/acpi.rs (must apply cleanly to upstream)
- `P2-init-acpid-wiring.patch` adds 41_acpid.service and pcid-spawner retry logic
(acpid spawn removal is in P2-boot-runtime-fixes, do NOT duplicate)
- `P2-init-acpid-wiring.patch` adds 41_acpid.service and driver-manager retry logic
(acpid spawn removal is in P2-boot-runtime-fixes, do NOT duplicate; the historical
pcid-spawner retry logic was replaced when pcid-spawner was retired 2026-07-24)
When reordering patches, test the FULL chain: remove source, rebuild, verify.
local/docs/QT6-WAYLAND-NULL8-DIAGNOSIS.md
+3 -3
View File
@@ -7,7 +7,7 @@ performed in this diagnosis pass — host contention constraints honoured.
**Date:** 2026-07-20
**Branch:** 0.3.1
**Scope:** Phases A–C of `WAYLAND-IMPLEMENTATION-PLAN.md` § "Current Blocker"
**Scope:** Phases A–C of `3D-DESKTOP-COMPREHENSIVE-PLAN.md` § "Current Blocker"
---
@@ -272,14 +272,14 @@ locations claim the crash is "verified FIXED" via commits `de2d74c37e` +
have been of a greeter running WITHOUT the Wayland plugin (offscreen QPA),
not WITH the patched Wayland plugin.
3. **Stale-sysroot rebuild chain.** The `WAYLAND-IMPLEMENTATION-PLAN.md:157-171`
3. **Stale-sysroot rebuild chain.** The `3D-DESKTOP-COMPREHENSIVE-PLAN.md` § "Stale-sysroot rebuild chain"
documents that "Modifying only libwayland does NOT update qtbase's static
copy of `libwayland-client.a`. The old binary persists in qtbase's sysroot."
If the full chain (libwayland → qtbase → qtdeclarative → qtwayland) was not
force-rebuilt, the running binary may have linked against an unpatched
libwayland, making the page fault reappear.
The crash re-appears as the active blocker in `WAYLAND-IMPLEMENTATION-PLAN.md`
The crash re-appears as the active blocker in `3D-DESKTOP-COMPREHENSIVE-PLAN.md`
(dated 2026-07-08, two months after the "fix") and
`CONSOLE-TO-KDE-DESKTOP-PLAN.md:234` (2026-06-20, "WIRED, UNVALIDATED"). The
"verified FIXED" line at `CONSOLE-TO-KDE-DESKTOP-PLAN.md:43` directly