vasilito
19a9eecb54
Add a real, QEMU-targeted virtio-input driver as a new Red Bear recipe at local/recipes/drivers/virtio-inputd/. The driver handles virtio-input-host-pci, virtio-input-keyboard, virtio-input-mouse, and virtio-input-tablet devices and closes Gap #19 of the v5.0 desktop plan. The driver: * Walks the PCI capability list to find the modern virtio 1.0 capability block (common_cfg, notify_cfg, isr_cfg, device_cfg) using MmioRegion mappings via redox-driver-sys. Rejects legacy virtio-input (device 0x1052) which lacks the modern transport. * Negotiates VIRTIO_F_VERSION_1 only (the only required feature). * Allocates one event virtqueue (size up to 64) backed by four DMA buffers (desc, avail, used, event_buffers) and pre-fills the avail ring. * Polls the used ring at 60 Hz, drains completed events, decodes each virtio_input_event (8-byte type/code/value), and recycles drained buffers back to the avail ring. * Translates events to orbclient format and pushes them to inputd via ProducerHandle (Orbital path): - EV_KEY -> KeyEvent (with US-QWERTY character mapping) - EV_REL -> MouseRelativeEvent (REL_X/REL_Y) or ScrollEvent (REL_WHEEL) - EV_SYN -> dropped (inputd multiplexes) - Other -> dropped (Phase 5.2 will add evdevd path) Probe-time checks: * Vendor 0x1AF4, device_id >= 0x1042, revision >= 1 * Caps include a device_cfg block with virtio type == 18 (virtio_input) Configuration: a pcid-spawner fragment is added to config/redbear-full.toml under /etc/pcid.d/virtio-inputd.toml matching class=0x09 vendor=0x1AF4 with device_id_range 0x1042..=0x107F (and a separate 0x1052 entry that the driver intentionally rejects). Verification: cargo check produces 0 errors and 65 warnings, all of which are unused input-event-codes.h constants reserved for the Phase 5.2 expansion. Linking the binary requires the Redox cross-toolchain (relibc provides redox_sys_call_v0); this is provided by the build system, not the host toolchain. Plan: this is Phase 5.1 of CONSOLE-TO-KDE-DESKTOP-PLAN.md v5.0. The plan is updated to v5.1 with: (a) a 'What Changed Since v5.0' section, (b) Gap #19 marked DONE, (c) Phase 5 row marked DONE with sub-task status, (d) Gate E updated, (e) Input pipeline section updated to reflect the (c) path is now implemented. Phase 5.2 (evdevd producer path + virtio-snd) is documented as the next planned work but not yet implemented.
Red Bear OS
A microkernel operating system written in Rust, derived from Redox OS
What is Red Bear OS?
Red Bear OS is a general-purpose, Unix-like operating system with a microkernel architecture, written in Rust. It is a full fork of Redox OS, frozen at release 0.1.0, with added hardware support, filesystem drivers, and a KDE Plasma desktop path.
Goals:
- AMD & Intel parity — first-class support for both platforms on bare metal
- KDE Plasma desktop — Wayland-based desktop environment via the KWin compositor
- Hardware GPU acceleration — AMD GPU (amdgpu) and Intel GPU drivers via
redox-drm - Modern subsystems — USB, Wi‑Fi, Bluetooth, ext4, GRUB, D-Bus
- Offline-first builds — reproducible from archived, BLAKE3-verified sources
Quick Start
Prerequisites
Linux x86_64 host with Rust nightly, QEMU, nasm, and standard build tools.
See the Redox Build Guide for full setup.
Build & Run
# Clone
git clone https://gitea.redbearos.org/vasilito/RedBear-OS.git
cd RedBear-OS
# Build and run the desktop target in QEMU
./scripts/run.sh --build
# Build a live ISO for bare metal
./scripts/build-iso.sh redbear-full
# Build the text-only recovery target
./scripts/run.sh --build --config redbear-mini
Repository Hosting
The canonical Red Bear OS Git server is Gitea at
https://gitea.redbearos.org/vasilito/RedBear-OS.git. GitHub is not a Red Bear OS source of
truth and must not be used for pushes, issues, releases, or project coordination.
Public Scripts
| Script | Purpose |
|---|---|
scripts/run.sh |
Build and run in QEMU (-b to build, -c <config> for target) |
scripts/build-iso.sh |
Build a live ISO for bare-metal boot |
scripts/build-all-isos.sh |
Build all live ISO targets |
scripts/network-boot.sh |
PXE network boot helper |
scripts/dual-boot.sh |
Dual-boot installation helper |
Config Targets
| Target | Type | Description |
|---|---|---|
redbear-full |
Desktop | Wayland + KDE + GPU drivers + D-Bus services |
redbear-mini |
Console | Text-only recovery / install target |
redbear-grub |
Console | Text-only with GRUB boot manager |
Current Status
Red Bear OS boots to a login prompt in QEMU with working wired networking, D-Bus system bus, hardware detection daemons, and filesystem support (RedoxFS, ext4, FAT).
| Area | Status |
|---|---|
| Boot (ACPI/x2APIC/SMP) | ✅ Bare-metal proven |
| Userspace drivers (PCI, storage, net) | ✅ Working in QEMU |
| D-Bus system bus + services | ✅ Working (login1, PolicyKit, UDisks, UPower) |
| ext4 / FAT filesystems | ✅ Compiles, installer-wired |
| POSIX gaps (relibc) | 🚧 Bounded Wayland-facing support |
| DRM/KMS display drivers | 🚧 AMD + Intel compile; HW validation pending |
| Wayland compositor | 🚧 Bounded proof; Qt6/KF6 clients crash at init |
| KDE Plasma desktop | 🔄 In progress (Qt6/KF6 compile; KWin/QML blocked) |
| Wi‑Fi / Bluetooth | 📋 Planned (architected, implementation pending) |
How It Works
Red Bear OS uses a userspace driver model — all drivers run as unprivileged daemons:
Kernel (microkernel)
└── schemes: memory, irq, event, pipe, debug
└── Driver daemons (userspace)
├── pcid → PCI enumeration
├── e1000d → Intel ethernet
├── xhcid → USB controller
└── vesad → Display framebuffer
The kernel provides minimal services (memory, interrupts, IPC). Everything else — filesystems, networking, graphics, input — runs in userspace.
Documentation
- Implementation Plan — roadmap and execution model
- Desktop Path Plan — kernel → DRM → Mesa → Wayland → KDE
- D-Bus Integration — session bus architecture
- USB Plan — USB stack design
- Wi‑Fi Plan — wireless architecture
- Bluetooth Plan — BT stack design
- Documentation Index — full doc map
Contributing
Red Bear OS uses a full fork model. Upstream Redox sources are frozen and archived. All custom work lives in local/:
local/
├── sources/ # Red Bear source forks (git repos, directly editable)
├── recipes/ # Custom packages (drivers, GPU, system)
├── docs/ # Integration and planning docs
└── scripts/ # Build, test, and release tooling
We welcome contributions made with or without AI assistance — we care about quality, not how the code was produced.
License
MIT — same as upstream Redox OS.