Hi Guys, I am trying to port EDK 2 shell (ShellPkg) into our(vendor) BIOS and am facing a few problems.
One of the Shell constructor function, ShellLibConstructorWorker() tries to locate and open protocol gEfiShellProtocolGuid which hasn't been installed yet. It only gets installed in the UefiMain() function (module entry point) by calling CreatePopulateInstallShellProtocol(). In our BIOS, we always call the constructor functions first followed by the entry point function and then finally the destructors during exit. As I said above, the constructor tries to open protocol gEfiShellProtocolGuid but fails to find it and thus exits with an ASSERT failure. Why doesn't EDK have the same problem ? Does it even call the constructors explicitly ? PS: I am new to UEFI development, so forgive me if my question seems rudimentary. Thanks. Nik ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
