Red Bear OS
cbd40e0d63
P0-A1 from USB-IMPLEMENTATION-PLAN.md v2. Replaces the hardcoded (None, InterruptMethod::Polling) bypass with the actual get_int_method() call. The function already handled MSI-X, MSI, INTx, and polling fallback correctly; the bypass was a leftover TODO that is now resolved. The IrqReactor::run_with_irq_file() path at irq_reactor.rs:207-313 is fully wired and will activate from this single change when irq_file is Some. No other code assumed polling-only semantics. Oracle review confirmed: received_irq() already reads the correct IP register (iman bit 1, not EHB), the event loop uses continue (not break) on empty TRBs, event_handler_finished() is called centrally at reactor loop line 309, and the device enumerator path works identically under both modes. Upstream commits e4aab167 and 7e3e841f appear to already be in the 0.1.0 baseline — verify with git log before cherry-picking. Commit 4d6581d4 (more timeouts) is recommended as a follow-up.
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.