Red Bear OS
c4d64756a2
Replaced stub handle_cursor() with real Intel GPU cursor plane support: pipe.rs: - Added CursorPlane struct with CURCNTR/CURBASE/CURPOS MMIO registers - CURCNTR (0x70080): enable/disable with ARGB8888 64x64 cursor mode - CURBASE (0x70084): GTT offset of cursor surface (page-aligned) - CURPOS (0x70088): signed 16-bit x/y screen position - CursorPlane::set_enabled(), set_base(), set_position() methods - Initialized in kabylake() constructor (Gen9 Kaby Lake register layout) - Added cursor: Option<CursorPlane> field to Pipe struct scheme.rs: - hw_cursor_size() now returns Some((64, 64)) — Intel standard - handle_cursor() enables/disables hardware cursor based on buffer presence and updates cursor position from CursorPlane state Previously: 'Intel GPU hardware cursor planes are not yet implemented. Software cursor rendering is handled by the console layer.' (dead stub) Cross-referenced from Intel PRM IHD-OS-KBL-Vol 2c-1.17 display register definitions. Compiles clean (31 pre-existing warnings).
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.