AI Briefing
KO

Fuzix OS

·2026.04.19 00:24

Key point

Fuzix 0.4 significantly cleans up networking, executable formats, and the build flow.

Details

Fuzix 0.4 kept the kernel core intact while making bug fixes and interface improvements, and in particular redesigned the networking layer into a more modularized structure. Going forward, this lays the groundwork for running networking in a different address space from the kernel even on 8-bit machines.

Executable file formats have also been cleaned up.

  • The 8080 / 8085 / Z80 binary formats were unified so that 8085 and Z80 can directly execute 8080 binaries.
  • 68HC11 / 6803 have different formats, but by aligning the syscall ABI, 68HC11 can run 6803 binaries.
  • The previously used temporary 32-bit Linux binflt approach was dropped in favor of a.out + extended relocation map, aiming for a stable format going forward.

Build and distribution have also been improved. The toolchain is still tricky to handle, but system builds can now produce a bootable image in one step with make diskimage. However, make clean is still strongly recommended when switching targets, and make kclean when changing kernel configuration or targets.

Naming has also been cleaned up.

  • N8VEM had its name updated to reflect the rebranding to Retrobrew.
  • RC2014 is distinguished as the product name, and RCbus as the bus standard.
  • The old rc2014-xyz series has now been changed to rcbus-xyz.

Support coverage is broad, but some are excluded or still being verified.

  • Systems excluded for now: Pentagon, Pentagon 1024, Scorpion
  • Items not yet tested: P112, SocZ80

Most of the documentation covers the list of supported processors and systems. It covers various families including 6303/6803, 6502/65C02/65C816, 6809, 68HC11, 68000, 8080, 8085, ARM, ESP8266, NS32K, and Z80/Z180/64180/Z84C1X, describing for each target the compiler used, constraints, required boards or memory configuration, and floating point support. Some are already usable in practice, while others are still in the process of being ported or are at a toolchain verification stage.

This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.

Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.