Red Bear OS
b7e7b55638
Cross-referenced with linux-7.1/drivers/usb/host/xhci-caps.h:46-54
(HCSPARAMS3) and :94-119 (HCCPARAMS2).
Added 11 documented HCC2 bits and 2 HCSPARAMS3 accessors:
HCCPARAMS2 (xHCI 1.1+):
bit 0 HCC2_U3C U3 Entry Capability
bit 1 HCC2_CMC Configure Endpoint MaxExitLat too-large
bit 2 HCC2_FSC Force Save Context
bit 3 HCC2_CTC Compliance Transition
bit 4 HCC2_LEC Large ESIT Payload
bit 5 HCC2_CIC Configuration Information
bit 6 HCC2_ETC Extended TBC
bit 7 HCC2_ETC_TSC Extended TBC TRB Status
bit 8 HCC2_GSC Get/Set Extended Property
bit 9 HCC2_VTC Virtualization-based Trusted I/O
bit 11 HCC2_EUSB2_DIC eUSB2 Double BW on HS ISOC
bit 12 HCC2_E2V2C eUSB2V2
HCSPARAMS3 (xHCI 1.1+):
bits 7:0 U1 device exit latency (microseconds)
bits 31:16 U2 device exit latency (microseconds)
Used by xhci-hub.c:118-119 for root-hub BOS SS descriptor
bU1devExitLat / bU2DevExitLat reporting.
All bits gated behind accessor methods on CapabilityRegs. init()
logs which bits are set so operators can see at a glance which xHCI
1.1 features the controller advertises. Future phases (P2-C, P3, P7)
will read these bits to gate behavior.
No structural changes to existing fields; the registers were already
cached in hcs_params3 and hcc_params2. This commit only adds
constants, accessors, and one log block at init.
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.