Red Bear OS
7286457ae2
Cross-referenced with Linux 7.1 drivers/usb/host/xhci-pci.c. main.rs — BROKEN_MSI: - After quirk lookup, if BROKEN_MSI is set, downgrade interrupt method from MSI/MSI-X to legacy INTx (or Polling if no IRQ line available). Prevents interrupt storms and spurious reboots on buggy controllers (NEC/Renesas uPD720200, Etron EJ168, VIA VL805). mod.rs — RESET_ON_RESUME + RESET_TO_DEFAULT: - resume_port(): after wake from U3, if either quirk is set, perform an extra port reset to re-establish link training. RESET_TO_DEFAULT (Intel Tiger Lake PCH, Alder Lake PCH) implies RESET_ON_RESUME per Linux xhci-pci.c init path. - Prevents USB 3.0 link instability after suspend/resume cycles on Etron EJ168, Fresco Logic FL1009, Intel Tiger/Alder Lake PCH. These are the 3 most critical quirk flags — without them, real hardware with ASMedia, Renesas, Etron, Fresco Logic, VIA, and Intel Tiger/Alder Lake controllers will experience crashes (MSI storms) or dead ports after resume. Previous quirk enforced: NO_SOFT_RETRY (scheme.rs:600). Previous quirk effectively enforced: AVOID_BEI (always false). Total quirk flags now RUNTIME-ENFORCED: 5/50 (+4 from 1).
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.