On Fri, Sep 06, 2013 at 12:00:53PM +0200, Laszlo Ersek wrote: > On 09/06/13 08:12, Michael Chang wrote: > > > Is it viable to check the DevicePathType and mercy those not > > expressible via qemu bootindices (like BDS_EFI_MESSAGE_MISC_BOOT) ? > > As no way to tell user want those entries or not, use a more > > conservative policy rather than aggresive .. > > What about this: > - mark all options that have been matched by some fw_cfg bootorder entry, > - after the usual matching/picking loop is complete, iterate over the > boot options, > - for each unmarked option: if it starts with HD() or PciRoot(), skip it > (user could have added it if he/she had wanted it); if it starts with > something else (no way for the user to specify), append it to the end. > (This should also keep relative ordering between such "unspecifiable" > entries.)
Looks good to me. And I think the usage cause is better for most users as they can remove those entries via efibootmgr if they don't want it, comparing to the frustrating experience of adding it back, but got killed again on next power up. Thanks for figuring the solution out. :) Michael > > Laszlo > ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
