TL;DR
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
Kevin Boone has published a series of instructional articles on developing bare-metal applications for UEFI-based PCs from a Linux workstation. The sequence covers compiling and linking, EFI system partitions, bootable media, and basic file handling; it is a technical guide, not a report of a new platform or product.
Kevin Boone’s UEFI programming guide sets out a five-part sequence for experienced Linux developers who want to build and run bare-metal applications on PC hardware. The articles cover the toolchain, boot media and basic file handling, offering a practical entry point to development that runs under UEFI firmware rather than as a conventional Linux program.
The series begins with compiling and linking, addressing the software tools and build steps required to produce an EFI application. It then moves to the EFI system partition and the creation of a bootable DVD or USB flash image. The listed parts are intended to be read in order, with each article relying on material introduced earlier.
Later installments include a section described as “A pragmatic digression” and an article on handling files through the UEFI Simple File Protocol. The supplied page description does not provide detailed instructions or technical specifications for each part, but identifies the subject areas the full sequence covers.
Boone says the articles are written for experienced Linux developers while assuming no prior knowledge of UEFI. The stated aim is to explain the tools and steps needed to develop from a Linux workstation for a PC-type computer with UEFI firmware.
A Practical Route Into UEFI Development
UEFI development involves a different starting point from ordinary application programming: developers must produce an EFI-compatible program and make it available through bootable media. Boone’s outline links those tasks into a single learning sequence, from building the program to preparing a disk image and accessing files.
That structure may help Linux developers explore low-level software without first needing to learn UEFI from unrelated references. The guide is also relevant to readers interested in how a PC starts software before an operating system takes over. Its scope, as described, is instructional; the source does not claim that the articles constitute a complete course or support for every firmware and computer.
Popular right now
Bose QuietComfort Wireless Noise-Cancelling Headphones, Cypress Green
KitchenAid Artisan 5-Qt Tilt-Head Stand Mixer – Almond Cream (KSM150PS)
Breville BES870XL Barista Express Espresso Machine
As an affiliate, we earn on qualifying purchases.
From Linux Workstation to EFI Media
The material focuses on a PC-type computer with UEFI firmware and a Linux machine used for development. UEFI provides the firmware environment in which an EFI application can run before, or independently of, a full operating system. The guide’s topic list reflects the practical stages involved: compile and link an application, place the necessary files on an EFI system partition, and prepare media from which the machine can start.
The page presents the articles as dependent installments rather than stand-alone introductions. Readers unfamiliar with UEFI are the intended learners, but Boone assumes they already have substantial Linux development experience. The source lists five parts and invites readers who have written responses to send a webmention; it does not describe a formal release schedule or a separate software product.
Limits of the Available Guide Details
The supplied source summary does not specify which compiler, linker, or build-system versions the articles use, nor does it describe compatibility testing across different UEFI implementations. It also gives no publication dates, so the currentness of any tool-specific instructions cannot be established from this material alone.
The page describes the guide’s intended coverage but does not establish that it addresses every PC, firmware configuration, or boot-media format. Readers would need to consult the individual articles for the exact commands, requirements, and limitations.
Follow the Series in Listed Order
The source page directs readers to begin with Part 1 on compiling and linking and continue through the EFI system partition and bootable-media articles before moving to file handling with the Simple File Protocol. Because the parts build on one another, following the listed order is the clearest next step for readers starting from no UEFI experience.
No further publication, update, or maintenance milestone is given in the supplied material. Readers should check the individual articles for their technical requirements and any notices about revisions before applying the instructions to a particular machine.
Key Questions
Who is the UEFI programming series for?
It is aimed at experienced Linux developers and assumes no previous knowledge of UEFI.
What topics do the articles cover?
The listed topics include compiling and linking, the EFI system partition, creating a DVD or USB flash image, a pragmatic digression, and file handling with the Simple File Protocol.
Should the articles be read in order?
Yes. Boone says each part relies on information from the preceding articles and may be difficult to follow out of sequence.
Does the guide provide instructions for every PC?
The supplied page description does not establish broad compatibility. Check the individual articles for their specific tools, commands, firmware assumptions, and limitations.
Source: kevinboone.me
