My point was
that I am only focused on booting linux, and so the legacy BIOS
is just flash baggage after linux gets going. Grub offers some booting
flexibility that I need, and since it is C code, also is more easily
customized for some other things I need to do during boot (embedded
Linuxbios + Etherboot, surely?
You can give the command line by hand from the serial console or via
DHCP. Start off with the NFS root, administered remotely. Then populate
the disk and for subsequent disk boots, Etherboot has an IDE driver. No
direct support for SCSI controllers, but I think you'll be hard pressed
to get that without legacy BIOS.
And you can set LinuxBIOS options to say you want to boot off of the
network of off of local IDE.
As for SCSI if you want it writing an etherboot driver should not be too bad...
Eric Biederman ported Etherboot directly to LinuxBIOS,
so no legacy BIOS
needed. It's mostly C and Ken Yap is talking about embedding lua
), so now would be a good time to talk about what
customisation you need.
I think that is mostly with regards to network loaded code, from
mknbi/mkelfImage or similiar.