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

docs(driver-manager): v5.9 records round-8 base/logd/ipcd/ftdi/acmd fixes

Browse Source 
v5.9 supersedes v5.8. Records:

- base 4ba51183 — logd kernel-log reader no longer breaks the
  loop on EOF (was silent data loss); logd read/fcntl/fsync now
  return ENOSYS or propagate errors instead of Ok(0) stubs;
  ipcd/uds/stream write backpressure applied in fevent when
  peer's rcvbuf is full; initfs tools probe page size at runtime
  (was hardcoded 4 KiB — breaks 16k/64k ARM systems).

- redbear-ftdi/redbear-acmd 27bbe13 — the four ftdi device-setup
  calls and the two acmd CDC-ACM setup calls now propagate errors
  via ? instead of  swallowing them. Device setup
  failure is now a hard error, not a silent misconfiguration.

All per local/AGENTS.md NO-STUB POLICY: every FIXME/TODO stub
in the round-8 scan scope was replaced with a real implementation
or a proper error return.

This is a doc-only commit (status header update); the actual
code fixes are already committed to submodule/base (4ba51183)
and the ftdi/acmd recipe heads (27bbe13), both pushed to origin.
This commit is contained in:
kellito
2026-07-27 08:40:41 +09:00
parent 27bbe13425
commit a405059aec
1 changed files with 15 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
local/docs/DRIVER-MANAGER-MIGRATION-PLAN.md
+15 -10
View File
@@ -1,15 +1,20 @@
# Red Bear OS — `pci-spawner` → `driver-manager` Migration Plan
**Document status:** v5.6 canonical planning authority (supersedes v5.5).
v5.6 records the round-5 compositor comprehensive fix (W1/W2/W3
from the round-4 audit + pre-existing compile errors) and the
SYSTEM-STABILITY → archived move. v5.5 recorded the round-4
stub-fix and stale-doc cleanup pass. v5.4 recorded the Mesa Redox
winsys CS submit seqno multi-process correctness fix. v5.3
records W2 closure. v5.2 closed C1. v5.1 closed G-A4. v5.0 closed
v5.3 (initnsmgr O_NONBLOCK) and the W1-W8 stub-fix pass. v4.9
recorded v5.0, v5.1, v5.5 implementation. v4.8 was the first
comprehensive cross-subsystem audit after the cutover completed.
**Document status:** v5.9 canonical planning authority (supersedes v5.8).
v5.9 records the round-8 base/logd/ipcd stubs and ftdi/acmd
setup-error fixes. v5.8 closed the round-7 relibc stubs
(set_scheduler, F_SETLKW, relative_to_absolute_foffset, setitimer,
ptrace) and bumped CONSOLE-TO-KDE to v6.0. v5.7 closed the
round-6 relibc stubs (semaphores, etc.). v5.6 records the round-5
compositor comprehensive fix (W1/W2/W3 from the round-4 audit +
pre-existing compile errors) and the SYSTEM-STABILITY → archived
move. v5.5 recorded the round-4 stub-fix and stale-doc cleanup
pass. v5.4 recorded the Mesa Redox winsys CS submit seqno
multi-process correctness fix. v5.3 records W2 closure. v5.2
closed C1. v5.1 closed G-A4. v5.0 closed v5.3 (initnsmgr O_NONBLOCK)
and the W1-W8 stub-fix pass. v4.9 recorded v5.0, v5.1, v5.5
implementation. v4.8 was the first comprehensive cross-subsystem
audit after the cutover completed.
The round-5 fix was non-trivial: redbear-compositor had
**pre-existing compile errors** (broken `?` operator on `()`,