On 02/12/14 22:49, Bill Paul wrote: > - If I use a version of my loader to create a correctly formatted BootXXXX > variable -- in this case Boot0006 -- and add it to the head of the BootOrder, > it's properly preserved across QEMU instances. > > - If I run the buggy version of the loader and create a bogusly formatted > BootXXXX variable and add it to the head of the BootOrder, it gets removed > somewhere along the line -- if I reset the emulator and hit a key to > interrupt > the boot process and go to the shell and use dmpstore -b Boot*, I can see > that > the Boot0006 variable has been deleted from the datastore and the BootOrder > variable has been updated as well. > > I'm not exactly sure what code/module is responsible for doing this (Bds?), > but clearly something is chucking the bad boot path variable out the window. > My suspicion is that the code on the hardware that I have is just older and > not as good about validating the boot paths,
I think this is a good assessment. I share your suspicion that the incorrect variable contents are caught in "IntelFrameworkModulePkg/Universal/BdsDxe" or "IntelFrameworkModulePkg/Library/GenericBdsLib", and that your hw vendor might have shipped a BDS that's less robust in this regard. In any case I'm glad that Jordan's flash variable work has borne fruit for FreeBSD (TCG) hosts too. Thanks Laszlo ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
