Red Bear OS
30819f87cf
If neither the IRQ line nor the scheme surface has produced activity for TX_WATCHDOG_SECS, log a warning. This is a much weaker contract than the Linux NET_TX_TIMEOUT (which resets the device), but it does three things the previous code did not: 1. Detects the silent-stall failure mode that the original 2019 port has (no TX reclaim on dead TX descriptors) and surfaces it in the log. 2. Forces the next event-loop iteration to call scheme.tick() which exercises the transmit ring. 3. Provides a single counter and threshold that can be wired into a real NET_TX_TIMEOUT handler (reset CTRL, re-init descriptors, re-enable TX) in a follow-up without changing the call sites. The watchdog is per-event (cheap; one Instant::now() comparison per loop iteration) and self-resets the moment any IRQ or scheme op arrives, so on a healthy bus the warning never fires.
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.