Red Bear OS
cca052338d
The existing init() resets the chip, sets up descriptor rings, and enables TX+RX. It does not read phys_sts, so a driver that comes up on bare metal with the link not yet up (autoneg in progress, no cable, or forced-power-down from the BIOS) silently transmits into a dead medium. Add a single phys_sts read at the end of init(). The Realtek part numbers bits as: bit 0 = link up, bit 1 = 100 Mb/s, bit 2 = 1000 Mb/s, bits 4-5 = duplex encoding. When the link is not up, log a warn!() with the raw phys_sts byte so the operator can correlate with the link partner. When the link is up, log the detected speed as info!(). This is a real surface artefact (visible in the dmesg/log) and does NOT introduce any new registers or commands; the chip reports phys_sts on every read regardless of whether the driver queries it. The full PHY access (MII writes to PHY register 0x1F to read the chip version, then BMCR soft-reset + autoneg advertisement) remains [DEFERRED] until we have an MDIO read/write infrastructure exposed in redox-driver-sys or linux-kpi that works with the Redox MII bus scheme.
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.