From a405059aec66cfa70e2997e5647c1306d9a8e508 Mon Sep 17 00:00:00 2001 From: kellito Date: Mon, 27 Jul 2026 08:40:41 +0900 Subject: [PATCH] docs(driver-manager): v5.9 records round-8 base/logd/ipcd/ftdi/acmd fixes MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- local/docs/DRIVER-MANAGER-MIGRATION-PLAN.md | 25 ++++++++++++--------- 1 file changed, 15 insertions(+), 10 deletions(-) diff --git a/local/docs/DRIVER-MANAGER-MIGRATION-PLAN.md b/local/docs/DRIVER-MANAGER-MIGRATION-PLAN.md index 20a41846e3..2f43240bd4 100644 --- a/local/docs/DRIVER-MANAGER-MIGRATION-PLAN.md +++ b/local/docs/DRIVER-MANAGER-MIGRATION-PLAN.md @@ -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 `()`,