From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MuCqq-0001TK-1H for qemu-devel@nongnu.org; Sat, 03 Oct 2009 18:13:16 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MuCql-0001M9-FP for qemu-devel@nongnu.org; Sat, 03 Oct 2009 18:13:15 -0400 Received: from [199.232.76.173] (port=45254 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MuCql-0001M1-Bb for qemu-devel@nongnu.org; Sat, 03 Oct 2009 18:13:11 -0400 Received: from mail-yw0-f176.google.com ([209.85.211.176]:45865) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MuCqk-0007SF-QQ for qemu-devel@nongnu.org; Sat, 03 Oct 2009 18:13:10 -0400 Received: by ywh6 with SMTP id 6so1504065ywh.4 for ; Sat, 03 Oct 2009 15:13:10 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <13426df10910031040y5029dc31m8c6ca4a4bac098a6@mail.gmail.com> References: <4AC4A487.1050003@us.ibm.com> <2a50f7880910011741k65ac8dfbq2fc8c9f58f5fa8d9@mail.gmail.com> <4AC60037.6000001@codemonkey.ws> <2a50f7880910020958g3fe5eadehe5e5094c05b218d9@mail.gmail.com> <4AC64A5C.6010003@gmx.net> <4AC64C32.4020509@codemonkey.ws> <4AC67326.6080603@gmx.net> <20091003150803.GF17326@redhat.com> <20091003173252.1061.qmail@stuge.se> <13426df10910031040y5029dc31m8c6ca4a4bac098a6@mail.gmail.com> Date: Sat, 3 Oct 2009 15:13:08 -0700 Message-ID: <2a50f7880910031513u713f7d52xc95847e9b248964b@mail.gmail.com> Subject: Re: [coreboot] [Qemu-devel] Release plan for 0.12.0 From: Jordan Justen Content-Type: text/plain; charset=ISO-8859-1 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: ron minnich Cc: Anthony Liguori , Gleb Natapov , Coreboot , qemu-devel@nongnu.org, Carl-Daniel Hailfinger On Sat, Oct 3, 2009 at 10:40, ron minnich wrote: > I use qemu for a lot of coreboot work. I really depend on qemu for > many things I do, not just coreboot related. The qemu target in > coreboot has been very heavily used by us to test out new ideas. > > That said, I don't see a compelling need to augment seabios with > coreboot on qemu *in the standard distribution*. If seabios gets the > job done, and gets OSes booted, I think that's sufficient. I don't see > a need to complicate anyone's life with something that is, after all, > a sideshow for qemu users. > > Conversely, I don't see the need to add the huge pile of stuff that > comes with UEFI/OVMF/whatever to qemu either. One might argue that This is a valid argument right now. OS X is the only OS today that targets UEFI, and specifically not legacy BIOS. But, in 5 ~ 10 years that might not be the case. I'll admit that this is a fairly dumb argument to make while we are talking about a QEMU release only a few months from now. But, as UEFI seems to be gaining ground in the industry, I think the sooner QEMU can get this support, the better. We're specifically trying to help out with this with OVMF. But if a better solution is developed, then so be it. > having any BIOS callbacks in the OS is a huge mistake, and certainly > I've learned in practice that this argument is true. I'm not going to take a side on this matter. But, I think what will be more important is what is used in the majority of OS's and systems. This is why we still put the 16-bit legacy BIOS as the #1 priority after ~30 years. But, like I mention, I think there are signs that this may shift towards UEFI at some point. -Jordan