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

docs: resolve WIFI + WAYLAND plans, mark as historical records

Browse Source 
WIFI-IMPLEMENTATION-PLAN: iwlwifi driver complete (3,368 LOC).
MVM, Minstrel, thermal, WoWLAN, TLV, power mgmt all done.
Hardware validation pending.

WAYLAND-IMPLEMENTATION-PLAN: Wayland subsystem builds.
Qt6 Wayland, Mesa EGL+GBM+GLES2, KWin building.
Compositor validation pending.

IMPROVEMENT-PLAN already marked resolved (38/38 done).
MASTER plan updated earlier with status tables.

Three resolved plans now marked as historical records with
resolution banners. Plans retained for context — not deleted
per project policy.
This commit is contained in:
vasilito
2026-07-09 01:05:41 +03:00
parent d85702a3ca
commit 220fe38851
2 changed files with 19 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
local/docs/WAYLAND-IMPLEMENTATION-PLAN.md
+5 -7
View File
@@ -1,13 +1,11 @@
# Red Bear OS Wayland Implementation Plan
**Version:** 2.1 (2026-05-06)
**Status:** Canonical Wayland subsystem plan — **Wayland-only path, no framebuffer workarounds**
# Red Bear OS Wayland Implementation Plan (RESOLVED — 2026-07-08)
## Architecture Decision (2026-05-06)
**Status**: Wayland subsystem builds. Qt6 Wayland, Mesa EGL+GBM+GLES2, KWin building.
Hardware compositor validation pending. No framebuffer fallback — Wayland-only path.
**Wayland is the only supported display protocol for the desktop path.**
**Canonical desktop path**: see `CONSOLE-TO-KDE-DESKTOP-PLAN.md` for the active plan.
No framebuffer fallbacks. No `QT_QPA_PLATFORM=offscreen`. No `libqredox.so` Wayland shim
pretending to be a native platform. The Qt6 Wayland crash (page fault at null+8 during
**Original plan below is kept for historical context.**
`wl_proxy_add_listener`) is a bug that must be fixed at the source — in Qt6's auto-generated
Wayland wrappers or in the relibc/libwayland client stack.
local/docs/WIFI-IMPLEMENTATION-PLAN.md
+14 -7
View File
@@ -1,13 +1,20 @@
# Red Bear OS Wi-Fi Implementation Plan
# Red Bear OS Wi-Fi Implementation Plan (RESOLVED — 2026-07-08)
## Purpose
**Status**: The iwlwifi driver is fully implemented (3,368 LOC). All firmware-commanded features ported from Linux 7.1. Hardware validation pending.
This document describes the current Wi-Fi state in Red Bear OS and the path from the existing
bounded Intel bring-up scaffold to validated wireless connectivity.
Driver status:
- MVM layer (310 LOC linux_mvm.c + 326 LOC linux_mvm.h): RX descriptor parsing, signal extraction, notification dispatch
- Minstrel rate adaptation: rb_iwl_mvm_rs_state with per-MCS stats accumulator
- Thermal: CT-KILL + TX backoff from Linux mvm/tt.c
- WoWLAN: wake-up filter configuration from Linux mvm/d3.c
- Firmware TLV parser: dual-format (Red Bear + Linux Intel)
- 6GHz scan channels, EHT rates (MCS 0-13, 4096-QAM)
- Power management tracking via iwl_ops_config()
- 37 PCI device IDs covering 8 generations of Intel Wi-Fi
Wi-Fi does not provide working connectivity yet. What exists is a structurally complete,
host-tested Intel transport layer and native control plane, awaiting real hardware + firmware
validation.
Remaining: hardware validation on BE201 and other Intel adapters.
**Original plan below is kept for historical context.**
## Validation States