From: Klemens Nanni <kn@openbsd.org>
Subject: new net/ipxe
To: ports <ports@openbsd.org>
Date: Sat, 22 Nov 2025 11:48:33 +0000

The port itself supports any architecture, but builds only amd64 and arm64
as others have not been tested (riscv64 and loongson might be of interest).

It requires GNU tools incl. compiler and linker, we have everything except
- ports@ "binutils: enable ld.bfd ?"

Once all knobs and found and set properly, GNU make compiles all files
always compiles all files (see https://dox.ipxe.org/ifdef_harmful.html)
and then links targets according to config.

I want to be able to serve images for several architectures from a single
netboot server and avoid cross compilation, so this port uses MACHINE_ARCH
in PKGNAME and sets PKG_ARCH=*;  per-arch files don't conflict and even
per-platform (e.g. EFI or BIOS) files seem to end up with unique tuples
of what upstream calls drivers and extensions, see Files below as well as
https://ipxe.org/appnote/buildtargets.

Then I can serve, e.g. ipxe.efi over TFTP or HTTP and further do whatever
on the clients, for example through autoexec.ipxe, which it tries to load
from the server by default.


Feedback? OK?

$ pkg_info -d -L ipxe-amd64                
Information for inst:ipxe-amd64-1.21.1pl1229

Description:
iPXE builds for these platforms:  efi pcbios

Changes to the default configuration:
- enable HTTPS, see https://www.ipxe.org/crypto
- raise minimum TLS version to 1.2

Maintainer: Klemens Nanni <kn@openbsd.org>

WWW: https://ipxe.org

Files:
/usr/local/share/ipxe/amd64/ipxe.efi
/usr/local/share/ipxe/amd64/snp.efi
/usr/local/share/ipxe/amd64/snponly.efi
/usr/local/share/ipxe/amd64/undionly.kpxe
/usr/local/share/ipxe/amd64/undionly.lkrn
/usr/local/share/ipxe/amd64/undionly.pxe
/usr/local/share/ipxe/amd64/undionly.usb