Red Bear OS
bd379e0771
Port the Linux 7.1 hub.c port state machine into usbhubd, replacing the minimal connect/reset handling: New module port_ops.rs (pure logic, side effects injected, 14 unit tests): - debounce_until_connected: hub_port_debounce_be_connected() port (hub.c:4696-4737) — 25ms polls, connection stable for 100ms, 2s budget, connection-change bit cleared in-loop. - wait_for_reset: hub_port_wait_reset() port (hub.c:2953-3047) — 10ms polls until RESET clears with CONNECTION set, escalate to 200ms after two short waits, 800ms budget; then 50ms TRSTRCY recovery (hub.c:3159) and C_PORT_RESET clear. Replaces the previous bare sleep(10ms). - wait_for_u0: USB 3.0 polling→U0 wait after port power-on — 36ms steps, 400ms ceiling (tPollingLFPSTimeout = 360ms; Linux hub.c:1226 debounce path). - accumulate_hub_delay_ns: wHubDelay chain rule (hub.c:1507-1519: wHubDelay + parent->hub_delay + 40ns, cap 65535ns). main.rs wiring: - Port status normalized to PortStatusSnapshot (decouples the state machine from the V2/V3 wire formats; V3 link state extracted from bits 8:5). - Debounce on connection-change before attach; C_PORT_ENABLE cleared once handled (Linux port_event semantics). - Reset path uses wait_for_reset instead of sleep(10ms). - USB 3 power-on path waits for U0 before proceeding. - wHubDelay: ancestor-chain walk fetching USB 3 ancestor hub descriptors, accumulated per Linux; delivered to newly attached SuperSpeed children via SET_ISOCH_DELAY (USB 3.0 9.4.11; Linux message.c:1142 — hubs and non-SS skipped, children inherit the hub's accumulated delay verbatim per hub.c:5128-5129). - attach/detach failure logs now identify the port. hub.rs (xhcid usb module): - HubDescriptorV3 extended with device_removable: u16 — the SS hub descriptor is 12 bytes (spec Table 10-15); the old struct under-read by 2 bytes. Stale TODO corrected: SS descriptors have no PortPwrCtrlMask (that is USB 2.0-only, still unparsed). Verified: cargo check clean (0 usbhubd warnings), 14/14 usbhubd tests, xhcid unaffected (43/43 tests).
Base
Repository containing various system daemons, that are considered fundamental for the OS.
You can see what each component does in the following list:
- audiod : Daemon used to process the sound drivers audio
- bootstrap : First code that the kernel executes, responsible for spawning the init daemon
- daemon : Redox daemon library
- drivers
- init : Daemon used to start most system components and programs
- initfs : Filesystem with the necessary system components to run RedoxFS
- ipcd : Daemon used for inter-process communication
- logd : Daemon used to log system components and daemons
- netstack : Daemon used for networking
- ptyd : Daemon used for pseudo-terminal
- ramfs : RAM filesystem
- randd : Daemon used for random number generation
- zerod : Daemon used to discard all writes and fill read buffers with zero
How To Contribute
To learn how to contribute you need to read the following document:
If you want to contribute to drivers read its README
Development
To learn how to do development with these system components inside the Redox build system you need to read the Build System and Coding and Building pages.
How To Build
It is recommended to build this system component via the Redox build system, you can learn how to do it on the Building Redox page.
To build and test outside the build system, install redoxer then use check.sh script to build or test:
./check.sh- Check build for x86_64./check.sh --arch=ARCH- Check build for specific ARCH (aarch64,i586,riscv64gc)./check.sh --all- Check build for all ARCH./check.sh --test- Check the base system boots up on x86_64
You can also use make install to inspect the content on ./sysroot, or make test-gui to test booting with orbital interactively.