On Oct 9, 2014, at 5:18 AM, [email protected] wrote:
> 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.
>
The DXE Core dispatcher has a protocol notify event,
CoreFwVolEventProtocolNotify(), on gEfiFirmwareVolume2ProtocolGuid. This is the
code that detects a FV in an FV. Depex is supported so you can defer the
processing of the FV based on a Depex.
https://svn.code.sf.net/p/edk2/code/trunk/edk2/MdeModulePkg/Core/Dxe/Dispatcher/Dispatcher.c
When the DXE Core launches it discovers FVs via EFI_HOB_TYPE_FV, see
FwVolBlockDriverInit() in
https://svn.code.sf.net/p/edk2/code/trunk/edk2/MdeModulePkg/Core/Dxe/FwVolBlock/FwVolBlock.c
So any EFI_HOB_TYPE_FV produced in PEI should cause the DXE Core to see an FV.
In the DXE phase an FV is added via gDS->ProcessFirmwareVolume().
From looking at the DXE Core code in FwVolBlock.c it looks like if the HOB
points to a bad FV you don’t get any error messages, even on a debug build.
Thanks,
Andrew Fish
Thanks,
Andrew Fish
> 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
------------------------------------------------------------------------------
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
