SWONE

SWONOS Kernel

Current development status: SWONOS Kernel 0.3.3 – fully validated on physical hardware.

SWONOS Kernel

Current development status: SWONOS Kernel 0.3.3 – fully validated on physical hardware.

The SWONOS Kernel is built through traceable development stages. New versions are created, booted and checked for errors. Its current technical release identifier is 100.3.3-swonos-kernel.

Independent kernel development

The development branch includes proprietary kernel functions, device objects and a PCI/PCIe device layer.

First external Windows driver running

Version 0.2.2 successfully executed an external Windows PCI/PCIe reference driver on real hardware for the first time. This is an important step beyond device identification alone.

Proven — but not universal

The successfully executed driver is an unmodified AMD64 reference driver built using Microsoft's official WDK. The original Realtek OEM driver is not yet supported. General Windows driver compatibility remains a development goal.

Development timeline

The most important milestones successfully achieved in SWONOS development.

System
September 2026

Dedicated SWONOS system interface

Customisations to the desktop, Start menu, login screen and system design are integrated into the development environment.

Boot PASS
8–9 October 2026

First custom kernel versions boot successfully

SWONOS Kernel 0.0.1 and 0.0.2 pass their final boot and regression tests.

Tests PASS
October 2026

Custom kernel functions pass self-tests

Versions 0.0.3 through 0.0.5 extend SWONOS NT Core with status, Unicode, list, event and synchronisation functions as well as driver and device objects. All self-tests pass.

Proof of concept
October 2026 · 0.1.4

Basic feasibility of driver integration demonstrated

Kernel 0.1.4 provides an important technical proof of concept for the planned driver support.

Hardware test
October 2026 · 0.1.6

Driver development tested with a real printer

Version 0.1.6 takes device and driver development beyond simulation: a printer using a Windows driver is used for a practical hardware test.

Validated
14 October 2026

SWONOS Kernel 0.2.0 validated

Kernel 0.2.0 is successfully completed and validated. At the same time, the technical foundation for the dedicated SWONOS update repository is created.

Hardware identified
15 October 2026 · 0.2.1

PCI/PCIe device detection and INF matching implemented

SWONOS identifies a real Realtek RTS5229 card reader using the hardware ID 10ec:5229. Windows INF matching finds a suitable driver candidate via the subsystem ID. This demonstrates successful device detection and driver matching in practice.

Approved
15 October 2026 · 0.2.1

Dedicated kernel release identifier introduced successfully

Kernel 0.2.1 uses its own identifier, 100.2.1-swonos-kernel, and passes final acceptance testing. Development of version 0.2.2 is approved.

Driver running
16 October 2026 · 0.2.2

First external Windows PCI/PCIe driver runs on real hardware

An independent AMD64 reference driver from Microsoft's official WDK runs unmodified on real PCI/PCIe hardware through SWONOS driver integration. Kernel 0.2.2 passes full acceptance testing.

Validated
16 October 2026 · 0.2.4

SWONOS Kernel 0.3.3 validated on physical hardware

Kernel 0.2.4 passed boot, PCI, WDM, KMDF, HID/PnP and S3/resume regression tests without panic, oops or resource leaks; taint delta 0. NT handle infrastructure and ZwCreateFile, ZwReadFile, ZwWriteFile and ZwClose passed testing. The Intel HID OEM import gap was reduced from 4 to 0. OEM driver execution has not yet been authorised for safety reasons: the KMDF function table and real ACPI/HID lower stack require further validation. The Linux driver remains active.

Validated · 26 October 2026 · 0.3.3
26.10.2026 · 0.3.3

SWONOS Kernel 0.3.3: physical HID hotplug validated

Kernel 100.3.3-swonos-kernel handles physical USB mouse removal and reconnection through the existing driver stack. The unchanged Insyde OEM filter driver reattached after both reconnect cycles and consumed real mouse movement. Boot PASS, taint delta 0. This is a targeted hardware validation, not general Windows driver compatibility.