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

docs: update public driver-manager handoff language

Browse Source
This commit is contained in:
Vasilito
2026-05-09 01:33:56 +01:00
parent 4c6a53c76d
commit e839007b6f
3 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/01-REDOX-ARCHITECTURE.md
+5 -3
View File
@@ -118,11 +118,13 @@ All drivers are **userspace daemons** that access hardware through:
**Network**: e1000d (Intel GigE), rtl8168d (Realtek 8168/8169/8125 path), ixgbed (Intel 10G), virtio-netd (VirtIO) **Network**: e1000d (Intel GigE), rtl8168d (Realtek 8168/8169/8125 path), ixgbed (Intel 10G), virtio-netd (VirtIO)
The native wired stack in this tree is userspace end to end: `pcid-spawner` autoloads NIC daemons, The native wired stack in this tree is userspace end to end: `driver-manager` autoloads NIC daemons
from `/usr/lib/drivers.d`/`/etc/drivers.d` match tables,
drivers expose `network.*` schemes through `driver-network`, `smolnetd` provides the `ip`/`tcp`/ drivers expose `network.*` schemes through `driver-network`, `smolnetd` provides the `ip`/`tcp`/
`udp`/`icmp`/`netcfg` schemes, and `dhcpd` plus config files under `/etc/net/` supply runtime `udp`/`icmp`/`netcfg` schemes, and `dhcpd` plus config files under `/etc/net/` supply runtime
addressing. Red Bear additionally ships a small native `netctl` compatibility command for profile- addressing. `pcid-spawner` is retained only as a compatibility alias for older init ordering and
driven wired setup. diagnostic language. Red Bear additionally ships a small native `netctl` compatibility command for
profile-driven wired setup.
**Audio**: ac97d, ihdad (Intel HD Audio), sb16d (Sound Blaster) **Audio**: ac97d, ihdad (Intel HD Audio), sb16d (Sound Blaster)
docs/04-LINUX-DRIVER-COMPAT.md
+1 -1
View File
@@ -195,7 +195,7 @@ pub struct PciDevice {
} }
pub fn enumerate() -> Result<Vec<PciDevice>> { pub fn enumerate() -> Result<Vec<PciDevice>> {
// Read from pcid-spawner or scheme:pci // Read from scheme:pci after driver-manager handoff
// Parse PCI configuration space for each device // Parse PCI configuration space for each device
// Filter to GPU devices (class 0x030000-0x0302xx) // Filter to GPU devices (class 0x030000-0x0302xx)
} }
docs/README.md
+1 -1
View File
@@ -108,7 +108,7 @@ This summary is only a quick orientation layer. For canonical current-state deta
- **Mesa**: software-rendered path is present; full GBM / hardware-validated Wayland path is still incomplete. - **Mesa**: software-rendered path is present; full GBM / hardware-validated Wayland path is still incomplete.
- **GPU drivers**: redox-drm scheme daemon exists; Intel build-oriented path exists; AMD currently has a bounded retained compile path (`redox-drm` + Red Bear glue) while the imported Linux AMD DC/TTM/core trees remain builds and included in redbear-full (2026-04-29). Hardware validation is still pending. - **GPU drivers**: redox-drm scheme daemon exists; Intel build-oriented path exists; AMD currently has a bounded retained compile path (`redox-drm` + Red Bear glue) while the imported Linux AMD DC/TTM/core trees remain builds and included in redbear-full (2026-04-29). Hardware validation is still pending.
- **Input**: evdevd compiled, libevdev built, libinput 1.30.2 built - **Input**: evdevd compiled, libevdev built, libinput 1.30.2 built
- **Networking**: native wired stack present (`pcid-spawner` → NIC daemon → `smolnetd`/`dhcpd`/`netcfg`), Red Bear ships a native `netctl` command, RTL8125 is wired into the existing Realtek autoload path, and the bounded Intel Wi‑Fi path now has host-tested profile start/stop plus interface-specific DHCP handoff without claiming real wireless connectivity. - **Networking**: native wired stack present (`driver-manager` → NIC daemon → `smolnetd`/`dhcpd`/`netcfg`, with `pcid-spawner` retained only as a compatibility alias), Red Bear ships a native `netctl` command, RTL8125 is wired into the existing Realtek autoload path, and the bounded Intel Wi‑Fi path now has host-tested profile start/stop plus interface-specific DHCP handoff without claiming real wireless connectivity.
- **PCI / IRQ quality**: architecturally strong substrate exists, with bounded MSI-X, IOMMU, xHCI IRQ, and low-level-controller proof surfaces; broader hardware robustness is still intentionally tracked as open work in `../local/docs/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md` - **PCI / IRQ quality**: architecturally strong substrate exists, with bounded MSI-X, IOMMU, xHCI IRQ, and low-level-controller proof surfaces; broader hardware robustness is still intentionally tracked as open work in `../local/docs/IRQ-AND-LOWLEVEL-CONTROLLERS-ENHANCEMENT-PLAN.md`
- **Wi-Fi profile target**: `config/redbear-wifi-experimental.toml` is the first explicit tracked image slice for bounded Intel Wi‑Fi validation, instead of spreading that claim across the generic desktop profiles. - **Wi-Fi profile target**: `config/redbear-wifi-experimental.toml` is the first explicit tracked image slice for bounded Intel Wi‑Fi validation, instead of spreading that claim across the generic desktop profiles.
- **Bluetooth**: one bounded in-tree BLE-first experimental slice exists, and the Battery Level read-only workload now has a packaged in-guest checker plus a host QEMU harness; QEMU validation is still in progress, so broad desktop Bluetooth parity is still incomplete - **Bluetooth**: one bounded in-tree BLE-first experimental slice exists, and the Battery Level read-only workload now has a packaged in-guest checker plus a host QEMU harness; QEMU validation is still in progress, so broad desktop Bluetooth parity is still incomplete