Red Bear OS
ad4bedd46d
maybe_recover_transfer_error previously handled only the first-tier codes (UsbTransaction, Resource, Stall, BabbleDetected, DataBuffer, Trb, SplitTransaction) and silently returned Ok(false) for every other completion code via a catch-all arm. Cross-referenced Linux 7.1 drivers/usb/host/xhci-ring.c handle_tx_event() (line 2608+) and handle_transferless_tx_event() (line 2561+) to add explicit recovery for the remaining ~29 codes: - Stopped/StoppedLengthInvalid/StoppedShortPacket: restart endpoint + retry (up to MAX_SOFT_RETRY), then hard-reset - InvalidStreamType/InvalidStreamId: soft reset + retry, then hard-reset - IncompatibleDevice: disable slot (device must re-enumerate) - MissedService/NoPingResponse: log informational, surface to caller - ContextState/Parameter: hard-reset to resync driver/xHC state - Bandwidth/BandwidthOverrun/SecondaryBandwidth: log, no transfer recovery (config must change) - IsochBuffer: hard-reset endpoint - MaxExitLatencyTooLarge: log, surface - EventLost/Undefined: hard-reset (event ring may be corrupted) - SlotNotEnabled/EndpointNotEnabled/NoSlotsAvailable: log driver state mismatch - CommandRingStopped/CommandAborted: log xHC state confusion - Reserved/vendor: default arm logs explicitly Added completion_code_to_errno() mapping transfer completion codes to POSIX errnos matching Linux 7.1 semantics: Stall -> EPIPE BabbleDetected -> EOVERFLOW UsbTransaction/SplitTransaction/IncompatibleDevice -> EPROTO Trb -> EILSEQ DataBuffer -> ENOSR SlotNotEnabled/EndpointNotEnabled/NoSlotsAvailable -> ENODEV default -> EIO Rewrote handle_transfer_event_trb() to use the new errno mapping instead of always returning EIO. Added 14 unit tests covering all errno mappings and transfer event handling paths. Full suite (41 tests) passes.
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.