Red Bear OS
5d2d114bf9
Phase I (LG Gram 16 (2025) / Arrow Lake-H S-state work). This commit implements the full Linux 7.1 S-state AML method sequence in userspace acpid, plus stubs for s2idle (Modern Standby). The kernel-side s2idle wire (new AcpiVerb variants EnterS2Idle / ExitS2Idle) is the next step; see local/docs/SLEEP-IMPLEMENTATION-PLAN.md for the gap analysis. Changes: * FACS: add set_waking_vector / set_x_waking_vector methods. These let acpid write the firmware waking vector for S3 resume, mirroring Linux 7.1 drivers/acpi/acpica/hwxfsleep.c:92 (acpi_set_firmware_waking_vector). * FACS access: add facs_mut() mutable accessor on AcpiContext (single-writer by construction). * AML methods: add set_system_status_indicator() that calls \_SI._SST(n). The canonical values are 0=working, 1=waking, 2=sleeping, 3=sleep-context, 7=indicator-off. Mirrors Linux ACPI 6.5 §6.5.1 (System Status Indicator). * wake_from_s_state(): wrap \_WAK(n) with the full Linux wake sequence (\_SI._SST(2) before, \_SI._SST(1) after). Mirrors drivers/acpi/acpica/hwsleep.c:255-314. * enter_sleep_state(): only call \_TTS here; \_PTS + \_SST + PM1 writes remain in set_global_s_state (Phase D, no duplication). * s2idle: add enter_s2idle() and exit_s2idle() methods on AcpiContext. These prepare/finish the s2idle path on systems without \_S3 (LG Gram 2025). Currently a no-op for the kernel coordination; the AML \_WAK(0) sequence runs via wake_from_s_state(0) on exit. Cross-references: * drivers/acpi/sleep.c (Linux 7.1) — acpi_suspend_begin/enter * drivers/acpi/acpica/hwxfsleep.c — acpi_enter_sleep_state_prep * drivers/acpi/acpica/hwsleep.c — acpi_hw_legacy_wake * kernel/power/suspend.c — s2idle_loop, s2idle_state * drivers/acpi/acpica/hwesleep.c — acpi_hw_execute_sleep_method Files changed: drivers/acpid/src/acpi.rs (+203 -14)
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.