On Fri, Nov 22, 2013 at 10:43 AM, Laszlo Ersek <[email protected]> wrote: > OTOH building all three FDs per default might be confusing for > end-users. We know for a fact that they usually don't read the README > (or not thoroughly enough). If we only give them one output file per > default, that's less potential for confusion.
If it will just add confusion, then perhaps it is something best left out of the README. And at that point, since splitting it is so easy, the value of having it in OVMF is debatable. > But I can certainly post a version where all three files are built per > default, if that's what you prefer (and aren't opposed to the idea in > general). I'm not opposed to it, but I would like to wait to see what QEMU does. Many of these scenarios were discussed in the past on qemu-devel, but a single -pflash was the only thing that stuck. This has made me just focus on making the single file pflash work. You also can't deny that the QEMU command line gets ugly real fast. Tangentially related idea: if the user specifies -pflash to a non-existent file, then QEMU could copy 'pflash-$(arch).bin' from the roms folder into that file, and then the use it for the flash. It could make using a flash almost as easy as using the default bios. -Jordan ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
