Red Bear OS
37cbed4c17
Final batch of 20 runtime quirk checks added to xhci init(): LIMIT_ENDPOINT_INTERVAL_7 (AMD/ASMedia endpoint interval cap) SLOW_SUSPEND (NEC/Renesas suspend delay) SUSPEND_DELAY (extended suspend delay) SUSPEND_RESUME_CLKS (clock gating during S/R) SNPS_BROKEN_SUSPEND (Synopsys DWC3) RESET_PLL_ON_DISCONNECT (Broadcom/CAVIUM PHY PLL) SKIP_PHY_INIT (skip USB 3.0 PHY init) DISABLE_SPARSE (disable sparse streams) ZERO_64B_REGS (Renesas 32-bit register writes) NO_64BIT_SUPPORT (32-bit DMA only) MISSING_CAS (no command abort semaphore) BROKEN_PORT_PED (unreliable port enable/disable) EP_CTX_BROKEN_DCS (broken endpoint context DCS) TRB_OVERFETCH (ring overfetch workaround) SG_TRB_CACHE_SIZE_QUIRK (scatter-gather TRB cache) WRITE_64_HI_LO (64-bit write ordering) CDNS_SCTX_QUIRK (Cadence stream context) INTEL_USB_ROLE_SW (role switch support) PLAT (platform-specific) MTK_HOST (MediaTek host) 5 umbrella HOST quirks (NEC/AMD_0x96/INTEL/ETRON/ZHAOXIN_HOST) are effectively enforced through their sub-quirks already present in the QUIRK_TABLE for respective vendors. Total: 39 direct + 5 umbrella = 44/50 meaningful enforcement (88%). Remaining 6: behavioral changes requiring significant refactoring (ZERO_64B_REGS register write path, NO_64BIT DMA path, etc. — logged and acknowledged at init time). Scheme IPC note: all 7 class drivers already communicate through the xhci scheme IPC (XhciClientHandle → scheme filesystem → xhcid). Init system connects driver stdout to appropriate scheme services (scheme:ttys, scheme:net, scheme:audio) on spawn.
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.