Red Bear OS
01cab772aa
First USB 2.0 Link Power Management implementation slice, cross-referenced with Linux 7.1 drivers/usb/host/xhci.c: xhci_set_usb2_hardware_lpm() and xhci-port.h. capability.rs: HCCPARAMS1 feature bit detection (Linux: HCC_*) - HCC_PPC (bit 3): Port Power Control - HCC_PIND (bit 4): Port Indicators - HCC_LHRC (bit 5): Light HC Reset - HCC_LTC (bit 6): Latency Tolerance Messaging - HCC_NSS (bit 7): No Secondary Stream ID - HCC_SPC (bit 9): Short Packet Capability - HCC_CFC (bit 11): Contiguous Frame ID - HCC_HLC (bit 19): USB 2.0 Hardware LPM Capability (xHCI 1.1+) port.rs: PORTHLPMC register bit definitions (Linux: xhci-port.h) - PORT_HLE: Hardware LPM Enable (bit 16) - PORT_HIRD_MASK, PORT_L1_TIMEOUT_MASK, PORT_BESLD_MASK - XHCI_DEFAULT_BESL = 4, XHCI_L1_TIMEOUT = 512us - Port::enable_lpm(hird, l1_timeout): programs PORTHLPMC - Port::disable_lpm(): clears PORTHLPMC mod.rs: - init() logs HCC1.HLC capability - LPM-aware quirk XHCI_HW_LPM_DISABLE gates LPM enable This makes USB 2.0 ports capable of entering L1 low-power link state when both the host controller and device support it. Actual LPM negotiation with devices (BESL, HIRD calculation, Evaluate Context for MEL) is deferred to P7 slice 2.
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.