I have not really checked the history and your recent changes in details. But until recently Intel BDS was requiring SMBios support. I sent a patch to fix this dependency: https://github.com/tianocore/edk2/commit/6d5b88f372180dc3a8622fda19ae0ac1fb0 76ae8
I also added support for Intel BDS to ArmVirtualizationPkg (enabled by the build flag INTEL_BDS). You can easily see the Intel BDS requirements by looking for 'INTEL_BDS' in the DSC and FDF files of this platform: https://github.com/tianocore/edk2/blob/master/ArmPlatformPkg/ArmVirtualizati onPkg/ArmVirtualizationQemu.dsc If you already have ArmPlatformPkg/Bds working on your platform, I would recommend you to start with this implementation of PlatformBdsLib: PlatformBdsLib|ArmPlatformPkg/Library/PlatformIntelBdsLib/PlatformIntelBdsLi b.inf > -----Original Message----- > From: Varad Gautam [mailto:varadgau...@gmail.com] > Sent: 28 October 2014 17:57 > To: edk2-devel@lists.sourceforge.net > Subject: [edk2] BeagleBoneBlackPkg: Moving to Intel BDS > > Hi, > > I'm configuring BeagleBoneBlackPkg [1] to use > IntelFrameworkModulePkg/Universal/BdsDxe. The build, after adding the > dependencies hangs at [2]. What does 291:`InstallProtocolInterface: > 348C4D62-BFBD-4882-9ECE-C80BB1C4783B 0` mean? Is HiiDatabaseDxe > expecting > a VFR form to load? Or does this indicate a missing module dependency? > > [1] > https://github.com/varadgautam/edk2/tree/kern/TexasInstrumentsPkg/Beagl > eBoneBlackPkg > [2] http://fpaste.org/145882/14517581/ > > Thanks, > Varad > > ----------------------------------------------------------------------- > ------- > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/edk2-devel ------------------------------------------------------------------------------ _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
