Skip to content
AevornixAEVORNIX
ComputeResearch

Aevornix OS

An operating layer for open computing.

Overview

What Aevornix OS is

Research into the operating layer for open devices: the system services, permission model, storage and networking interfaces, and application lifecycle that sit between the portable runtime and the machine.

Architecture position

Where this sits in the stack.

Portable and vendor-independent by construction: standard interfaces and open targets, so software moves across the ecosystem rather than binding to one platform.

RVStack architecture

RVStack architecture, 7 layers from top to bottom: 01 Application, 02 Development toolchain, 03 Portable runtime, 04 Operating layer, 05 RISC-V architecture, 06 Device profile, 07 Deployment target.

  1. Application
    Games, tools and software targeting the Aevornix platform.
    .aev project format
  2. Development toolchain
    Compiler, linker, debugger, SDK and build systems.
    ELFDWARF
  3. Portable runtime
    Execution services shared across supported RISC-V targets.
  4. Operating layer
    System services, permissions, storage, networking and application lifecycle.
    POSIX-style system interfaces
  5. RISC-V architecturefoundation
    The open instruction-set foundation beneath the software stack.
    RV64GCRVA23
  6. Device profile
    Defined hardware capabilities used for emulation and compatibility testing.
  7. Deployment target
    Physical devices, virtual environments, cloud targets and certified platforms.
    linux-riscv64

Open the full architecture →

The questions being researched

  • What an application may ask of a device, and how that is granted
  • How applications start, suspend, resume and are terminated
  • How storage and networking are presented consistently across profiles
  • What the operating layer must guarantee for the runtime above it

Position in the stack

This is layer 04 of the RVStack architecture: above the portable runtime and the toolchain, below the instruction set. Nothing here is implemented; the architecture position is the decided part.

Development

Where the work stands.

Objectives and dependencies. Dates appear only where a specific verifiable event backs them.

Research(1)

  • Research the system services, permission model and application lifecycle for open devices.

    Depends on
    Portable runtime
Aevornix OS | Compute | Aevornix