First steps in bare-metal programming using UEFI

233 points · 46 comments on HN · read original →

Points and comments are a snapshot, not live.

A series on building bare-metal UEFI applications from a Linux workstation, targeting experienced developers new to UEFI.

The articles cover compiling and linking UEFI applications, creating an EFI system partition, making bootable DVD or USB images, handling files via the Simple File Protocol, and pragmatic digressions such as the lack of a C standard library. The author assumes no prior UEFI knowledge but expects Linux development experience.

The series is intended to be read in order, as each part builds on earlier ones.

What commenters are saying

Commenters generally welcome the guide as a practical starting point. Several note UEFI's quirks: forced UTF-16 strings and VFAT filesystem are widely criticized as legacy burdens. One commenter suggests Multiboot2 as a saner alternative for bootloaders, and another recommends inspecting unresolved symbols with `nm -D --undefined-only`. A few defend FAT32 as a reasonable minimal filesystem choice. There is brief discussion of UEFI on ARM laptops and the distinction between "bare metal" and using UEFI firmware.