Question:
What must one do to get the DXE core to load a "random" Firmware Volume (FV)
and any drivers and/or legacy option ROMs (OROMs) it contains.
Background:
I am building a BIOS with EDK2.
I moved a UEFI driver and legacy OROM for a device from the main FV into one
devoted strictly to them (nothing else is in the FV). I placed that FV into
a second one that is compressed. The compressed FV is included in the FD
section of my FDF.
Before I moved these files around in the FDF, I would see the legacy OROM load
during POST. Now that they are in a separate FV, I no longer see the legacy
OROM load (I haven't looked at whether the UEFI driver loads yet, but I suspect
it does not).
I have searched the code for hours trying to locate where the FV HOB gets
populated, thinking that perhaps I have to add my new FV to some list; however,
I am unable to determine exactly where/how the FV HOB is initialized/populated.
Is this something I need to keep pursuing, or is there some other thing I must
do to get the DXE core to load my new FV and the drivers it contains?
Thanks,
Jim
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
