I just took a look at syslinux and all it really uses is are the PXE
UDP functions, that are currently implemented for freebsd support.
Though I believe it uses the 16bit API entry points.
PXE under EFI is a little different. UNDI is optional and it loads EFI
images, which only have a limited size due to implementation bugs.
So with a little care I think etherboot could implement pxe without
many changes. The task list would look like:
The todo list would be:
- Working 16bit PXE/32bit PXE glue code.
- Working raw download driver.
- [optional] PXE hacked DHCP.
- [optional] PXE TFTP.
- [optional] PXE UNDI compatibility.
Just in case someone is ambitious or has worries about shipping a
machine to someone who really wants PXE support.
Eric
|