Files
RedBear-OS/local/recipes
vasilito 8d2c2e34f0 round 17: iommu dead stubs removal + KMS module docs
Round 17 audit cleanup. Two main fixes plus one incidental update:

1. local/recipes/system/iommu/source/src/lib.rs — removed the entire
   host_redox_stubs module (341 lines, lines 815-1155). The module
   was guarded by #[cfg(not(target_os = 'redox'))] so it never compiled
   for Redox targets, but it ALSO failed to compile for host (Linux)
   builds because it used a 'libc' crate that isn't in iommu's
   Cargo.toml dependencies — 41 compile errors. Verified by:
     cargo check --target x86_64-unknown-linux-gnu
   before the deletion: 41 errors (all in host_redox_stubs).
   after the deletion: clean build, Finished 'dev' profile in 0.21s.

   The 21 redox_open_v1/redox_dup_v1/redox_kill_v1/etc. extern 'C'
   functions were supposed to provide host-side link table entries
   for the upstream-crates-io 'redox-scheme' crate. But:
     - iommu depends on the LOCAL redox-scheme fork
       (path = '../../../../../local/sources/redox-scheme')
     - the local fork doesn't call any of these symbols
     - even the upstream-crates-io version doesn't call most of them
   So the stubs were dead code that also happened to be broken.
   Removal cleans up 341 lines + makes the package host-buildable.

2. local/recipes/gpu/redox-drm/source/src/kms/{plane,crtc,connector}.rs —
   added module-level //! docstrings documenting that these modules
   are software-state models, not GPU-register-programming. Per the
   Round 16 audit, the gap between software-model validation and
   actual hardware programming lives in the per-driver backend
   (FakeDriver/IntelDriver/AmdDriver). Without these docstrings,
   a future maintainer might add hardware programming here and
   duplicate the driver-backend responsibilities.

3. local/docs/NETWORKING-AND-DRIVERS-SYSTEMATIC-ASSESSMENT-2026-07-27.md
   — incidental update (the operator's parallel work).
2026-07-27 22:43:31 +09:00
..