Red Bear OS
5276fcb739
Add support for HID Consumer page (usage page 0x0C) as key events.
Cross-referenced with Linux 7.1 drivers/hid/hid-input.c consumer
usage mapping.
Changes:
send_key_event() now handles usage_page 0x0C with a concrete
mapping table:
0x00E2 → scancode 0xF0 (Mute)
0x00E9 → scancode 0xF1 (Volume Up)
0x00EA → scancode 0xF2 (Volume Down)
0x00B0 → scancode 0xF3 (Play)
0x00B1 → scancode 0xF4 (Pause)
0x00B3 → scancode 0xF5 (Next Track)
0x00B4 → scancode 0xF6 (Previous Track)
0x00B5 → scancode 0xF7 (Stop)
0x00CD → scancode 0xF3 (Play/Pause)
0x0183 → scancode 0xF8 (AL Config)
0x018A → scancode 0xF9 (Email)
0x0192 → scancode 0xFA (Calculator)
0x0194 → scancode 0xFB (My Computer)
0x0221 → scancode 0xFC (Search)
0x0223 → scancode 0xFD (Home)
Event loop now dispatches usage_page 0x0C to send_key_event,
treating it identically to keyboard key press/release.
OrbKeyEvent.scancode is u8, so we use the 0xF0-0xFF vendor-key
block instead of the full Linux evdev encoding (0xC0000 | usage).
Cross-reference: Linux 7.1
- drivers/hid/hid-input.c: hidinput_configure_usage()
- include/uapi/linux/input-event-codes.h: KEY_VOLUMEUP, etc.
This means USB keyboards with media keys (Volume, Mute, Play/Pause,
Next/Previous Track) will now produce scancodes the display server
can map to media actions.
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.