Red Bear OS
b5f84b44df
acpi-rs (vendored fork): - _REG opregion connect (ACPICA evrgnini.c): run \_SB._REG(space, 1) per installed handler after \_INI — firmware gates EC access behind this. Device-level _REG for each device holding an OpRegion of an installed space. Fills the last big TODO in initialize_namespace. - RegionSpace: add From<RegionSpace> for u8 (region-space ID for _REG). acpid: - LPIT parser BUG FIX: GAS (Generic Address Structure) is 12 bytes (4-byte header + 8-byte address); the parser previously read entry_trigger/residency/latency/counter_frequency 4 bytes early and required length>=48 instead of 56. Fixed offsets, added entry_trigger_space_id, and mwait_hint()/best_mwait_hint() for the FFH MWAIT hint. Tests rewritten with correct 56-byte layout. - Thermal active cooling: /scheme/acpi/thermal/<zone>/active evaluates _AC0.._AC9 and returns defined trip points (tenths of K). - ACPI PM timer: pm_timer_read() from FADT pm_timer_block; /scheme/acpi/pmtimer endpoint (3.579545 MHz). - HW-reduced ACPI: Fadt::is_hardware_reduced() (FADT bit 20); skip PM1/GPE setup on such platforms. - General GPE dispatch: enabled_active_gpes() + \_GPE._Lxx/_Exx method evaluation (evgpe.c acpi_ev_gpe_detect).
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.