Hi, > Second thought on this. > > The main advantage to have a runtime Pcd over build time static > configuration is that we can use single binary for all OVMF use cases. > However currently Xen hvmloader statically embeds firmware blobs in > itself so it doesn't really matter if OVMF is configurable at runtime. > So this option will not benifit much unless we overhaul toolstack (libxl > and hvmloader) to support loading additional firmware blobs.
[ same goes for coreboot btw, there isn't much benefit in switching at runtime ] > > The only other option would be to move those modules to PcAtChipset. > > But, first we'd have to prove that QEMU & KVM are okay with using > > those drivers. > > > > I presume QEMU / KVM will still need enumeration, so they are not likely > to make use of those modules. Correct. cheers, Gerd ------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
