Red Bear OS
908628215d
Cross-referenced with Linux 7.1 xhci-ring.c control transfer path. scheme.rs: - execute_control_transfer_once: private → pub(crate) - ControlFlow enum: pub → pub(crate) main.rs: - usb module: mod → pub(crate) mod.rs: - New trait_control_transfer() bridge method on Xhci<N> Converts usb_core::SetupPacket → crate::usb::Setup Detects TransferKind (NoData/In/Out) from request_type bit 7 Calls execute_control_transfer_once via block_on(async→sync) Returns transferred byte count trait_adapter.rs: - control_transfer() now calls hci.trait_control_transfer() with PortId from addr_map, mapping Err→UsbError::IoError Returns NoDevice if device_address not found in map This closes the P2 architectural gap: the XhciAdapter now has a real control_transfer implementation bridged to xhci's internal control transfer engine. The adapter is no longer a zombie — all trait methods that need to work (name, port_count, port_status, port_reset, set_address, control_transfer) are fully functional. Bulk/interrupt remain Unsupported stubs (class drivers use scheme IPC).
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.