UCL (Universal Compatibility Layer)

Experimental fallback hardware compatibility framework for custom kernels and operating systems.

Project Overview

UCL is an experimental modular fallback hardware compatibility framework. Its goal is to help custom kernels and experimental operating systems boot and function on unsupported hardware using safe, generic compatibility runtimes.

It acts as an automatic safety net when vendor-optimized drivers are missing or fail.

Core Philosophy

1. Functionality First: The OS must boot and accept input.
2. Optimization Later: Performance is secondary to stability.
3. Fallback Compatibility over Vendor Perfection: Broad functionality without relying on reverse engineering.

What UCL Does

• Hardware Discovery: Actively enumerates PCIe, USB, ACPI, and other buses.
• Broad Capability Classification: Translates raw descriptors into functional categories (Storage, Display, Network, HID).
• Semantic Hardware Profiles: Caches known-safe registers and operational bounds.
• Safe Fallback Runtime Generation: Emits drivers constrained by physical safety bounds.
• Generic Runtimes: Out-of-the-box fallback implementations for Framebuffer rendering, HID input parsing, Block Storage abstractions, and minimal Networking.

What UCL DOES NOT Do

• Replace optimized vendor drivers: UCL is a fallback mechanism, not a replacement for official drivers.
• Provide GPU acceleration: You will not get Vulkan or OpenGL support here.
• Guarantee universal compatibility: Some complex hardware simply cannot run generically.
• Replace production kernels: This is an experimental research framework.

Current Status

Experimental Prototype. The architecture is fully validated, and integration tests (including QEMU orchestration) pass successfully.

Architecture

Discovery
   ↓
Classification
   ↓
Profiles
   ↓
Safety (Sandbox)
   ↓
Generator
   ↓
Fallback Runtime

Current Working Features

• PCI enumeration
• USB discovery (descriptor extraction)
• Rule-based hardware classification
• Profile caching and JSON serialization
• Generic Framebuffer (Basic text rendering fallback)
• Generic HID abstraction (Mouse/Keyboard byte-to-event parsing)
• Generic Storage abstraction (Block read/write)
• Sandbox safety layer (blocking dangerous MMIO zones)
• QEMU testing orchestration

Roadmap

• Real hardware validation
• Minimal experimental kernel integration
• Improved fallback networking
• ARM/mobile experimentation
• Runtime learning expansion