On Friday 21 May 2010 02:44:20 Jarrod Johnson wrote: > So in classic BIOS, something like gPXE gets to be the driver, the protocol > stack, and a boot loader. > > My impression was that in UEFI, the drivers for networking are distinct > from the protocol stack. > > Is there some document that clarifies what gPXE does in UEFI? Does it help > port drivers to be UEFI drivers, or does it do something fancier? In BIOS > world, I build an undionly.kkpxe to give me better protocol support without > replacing the firmware, does that use case map to uefi or am I currently > stuck with tftp without elilo/grub2 patches?
You can build an EFI driver (.efidrv), an EFI driver ROM (.efirom), or an EFI application (.efi). The EFI application allows you to use gPXE in the BIOS- familiar way, including the gPXE shell, multiple protocols, etc. Michael _______________________________________________ gPXE mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe
