Red Bear OS
9317d4874b
Two latent bugs exposed by test-usb-hub-qemu.sh against a real hub topology (QEMU usb-hub with usb-kbd behind it): 1. Status-change bitmap was indexed off by one: the loop checked bit (port - 1), but USB 2.0 spec 11.12.4 defines bit 0 = hub status change and bit N = port N status change (Linux hub_irq uses bit i for port i). Every change was processed on the wrong port — a device on port N was never enumerated (its bit was read as port N+1). 2. The event loop's first action was a blocking EP1 interrupt read; when the hub delivers no immediate status-change interrupt the daemon hung before ever scanning a port. Linux hub_activate() performs a full port scan before arming the status-change endpoint; the first iteration now forces an all-ports mask with the same semantics. Also widened the fallback all-ports mask to bits 1..=ports (bit 0 = hub, skipped).
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.