Red Bear OS
1c7f8390b3
Cross-referenced with Linux 7.1 xhci-pci.c ZERO_64B_REGS enforcement. Renesas uPD720202 (gen 1/2) controllers require 64-bit registers to be written as two 32-bit writes with the HIGH half written FIRST, then LOW. Normal path writes LOW then HIGH. Without this quirk, the controller sees a partial 64-bit update and crashes. Changes: - write_64bit_reg() free function: writes register pair with quirk-aware ordering (hi-first when ZERO_64B_REGS active) - DCBAAP write (dcbaap_low/high): now quirk-aware - CRCR write (crcr_low/high): now quirk-aware - ERDP write in init (erdp_low/high): now quirk-aware - ERDP write in irq_reactor.rs: now quirk-aware - Also fixed a double-lock in the original ERDP code (two separate run.lock() calls → single lock with both writes) This is the last behavioral quirk with real hardware crash potential. Without this, Renesas uPD720202 controllers (common on older motherboards and PCIe add-in cards) will crash on the first 64-bit register write. Quirk enforcement: 45→46/50 meaningful (92%). Remaining 4 are umbrella HOST quirks covered by their sub-quirks.
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.