tag
8 posts
An evidence-based guide to Haiku's separate ARM and ARM64 ports, their boot and driver work, build targets, and honest support claims.
FreeDOS's kernel is a from-scratch, clean-room reimplementation, and its authors' actual architecture choices differ deliberately from how MS-DOS was built.
A source-grounded map of Haiku's kernel: teams and threads, virtual memory, IPC, scheduling, modules, system calls, drivers, and debugging.
How Haiku's native API is divided into cooperating Kits, with shared conventions for messages, ownership, status codes, linking, and threads.
How Haiku BLoopers own dispatch contexts, BHandlers receive typed messages, BMessengers cross threads, and locking preserves state.
Why Haiku is a BeOS-compatible system with NewOS kernel roots and native Kits, despite its POSIX APIs, shell, ports, and Unix software.
A practical boundary between emulation and hardware-assisted virtualization, including CPU execution, devices, memory, timing, and hybrid systems.
How libretro separates emulator cores from frontends through a stable C API, callbacks, environment negotiation, serialization, and shared services.