Red Bear OS
0ca545d35a
Bounded WMI subsystem ported from Linux 7.1 drivers/platform/wmi/core.c and drivers/platform/x86/lg-laptop.c: - wmi.rs: guid_block (20-byte _WDG entry) parser, PNP0C14 device discovery (candidate-path _HID probe mirroring EC discovery), _WDG buffer read via aml_eval (AmlSerdeValue::Buffer), event-GUID enumeration (flags & ACPI_WMI_EVENT), _WED evaluation for eventcode decode, LG keymap (0x70 control-panel / 0x74 touchpad-toggle / 0xf020000 read-mode / 0x10000000 kbd-backlight). 4 unit tests cover guid_block parsing, event flag detection, short-input rejection, and keymap coverage. - power_events.rs: WMI notify handling in the AML notification drain — when a Notify fires on the WMI device, _WED is evaluated to decode the eventcode, mapped to a key name, and emitted as PowerEvent::Wmi. - main.rs: WMI discovery at init (after wake registry). PowerEvent::Wmi logged in the main loop. - acpi.rs: wmi_registry field on AcpiContext. Works on any x86 WMI laptop (LG, Dell, HP, Lenovo, ASUS, etc.). On QEMU (no PNP0C14) it is a no-op.
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.