Hi, Greg,

You can add the similar code in your project .fdf file to insert the prebuilt UEFI driver.

FILE DRIVER = 3d696f3f-b3e3-4ca6-b299-2e7e5c7986b7 {
  SECTION PE32 = $(PLATFORM_PACKAGE)/ThirdParty/IntelGopDriverRelease.efi
  SECTION UI   = "IntelGOP"
}

during DXE dispatching, the prebuilt UEFI driver can be found and loaded by calling ENTRY_POINT function, just like other UEFI drivers.
Binding E823-L NAC happens during the PCIe device enumeration, the function, EFI_DRIVER_BINDING_PROTOCOL.Supported() examines the binding criteria. You can load the prebuilt UEFI driver, but you can't use the driver for your device.

Best Regards

Feng Libo

Original:
Hi,

I am trying to automatically load an EFI file in EDK2, before the UEFI Shell is available. 

It is a prebuilt UNDI Network Driver from Intel,  E4297X8.EFI, from the complete Ethernet Drivers package zip file. ..\Release_29.3\APPS\EFI\EFIx64

The Open Source ICE driver doesn't contain bindings for the E823-L NAC  we have, even though it is part of the E800 series of Network Controller.

Is there a way to build an INF file, that doesn't have an entry point, to load the preexisting E4297X8.EFI file? I hope there is a way to "embed" it in the built payload, being loaded through Slimboot.

Kind regards.
 
Greg.

_._,_._,_
Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#121135) | | Mute This Topic | New Topic
Your Subscription | Contact Group Owner | Unsubscribe [rebecca@openfw.io]

_._,_._,_