Red Bear OS
c71e518391
Apply the same release/acquire fence pattern as e1000d and rtl8168d: - acquire fence before reading the RX status / length / data bytes, so the compiler does not reorder the buffer reads past the rxsts observation on weakly-ordered architectures. - release fence before the CAPR write (RX doorbell) so the device sees the buffer reads before the doorbell signals the consumer is done with the ring. - release fence before the TSD write (TX doorbell) so the device sees the buffer writes before claiming ownership of the descriptor. The 8139 is a legacy 100 Mb/s chip with a 64 KB ring rather than a 16-entry descriptor table, but the same hand-off semantics apply: ownership bit is cleared on read, set on write, and the device accesses buffer memory after the doorbell. The fences are the same compiler-level ordering the Linux 8139too driver places around its MMIO writes; the 8139 chip itself does not need anything more.
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.