From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Munyw-0004Ft-N0 for qemu-devel@nongnu.org; Mon, 05 Oct 2009 09:52:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Munyr-0004Dl-PS for qemu-devel@nongnu.org; Mon, 05 Oct 2009 09:52:06 -0400 Received: from [199.232.76.173] (port=52680 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Munyr-0004De-J7 for qemu-devel@nongnu.org; Mon, 05 Oct 2009 09:52:01 -0400 Received: from mail-yx0-f173.google.com ([209.85.210.173]:54945) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Munyr-0000NP-2Z for qemu-devel@nongnu.org; Mon, 05 Oct 2009 09:52:01 -0400 Received: by yxe3 with SMTP id 3so2854435yxe.4 for ; Mon, 05 Oct 2009 06:52:00 -0700 (PDT) Message-ID: <4AC9F9FD.60309@codemonkey.ws> Date: Mon, 05 Oct 2009 08:51:57 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [coreboot] [Qemu-devel] Release plan for 0.12.0 References: <4AC51DBA.7020609@codemonkey.ws> <4AC60037.6000001@codemonkey.ws> <2a50f7880910020958g3fe5eadehe5e5094c05b218d9@mail.gmail.com> <4AC64A5C.6010003@gmx.net> <4AC64C32.4020509@codemonkey.ws> <4AC67326.6080603@gmx.net> <2a50f7880910021528v742c39e8sd334b318c577fb71@mail.gmail.com> <4AC6872E.6060103@gmx.net> <2a50f7880910021732k68ae1a97qc7307ac52a225371@mail.gmail.com> <20091003173006.595.qmail@stuge.se> <2a50f7880910031449k13090dcdr8440d89ccb7fcfe9@mail.gmail.com> <1254607096.12717.10.camel@tetris> <4AC8F80C.2050702@us.ibm.com> <4AC8F9F2.3030508@coresystems.de> <4AC9EE84.1010803@us.ibm.com> <4AC9F34F.80105@gmx.net> In-Reply-To: <4AC9F34F.80105@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Carl-Daniel Hailfinger Cc: Anthony Liguori , Coreboot , Stefan Reinauer , qemu-devel@nongnu.org, ron minnich , Jordan Justen , Patrick Georgi Carl-Daniel Hailfinger wrote: > What about SeaBIOS + CSM (based on DUET)? That's not quite the same thing. In EFI, CSM is a specification that defines how to port a legacy BIOS such that it runs as basically an EFI module providing the old legacy BIOS interfaces that OSes support. If you have a set of legacy option roms and efi modules, it defines how all of those things interact with each other to provide a consistent experience. It's is not at all the same as just switching between EFI and BIOS. It's much more tightly integrated than that. > I can't speak for Patrick, but he probably was concerned about making > EFI the default with BIOS as fallback instead of the other way round. > Forcing any EFI capable (or semi-capable) OS to be booted with EFI > instead of leaving the choice in the hand of the user (NVRAM) or picking > the sane default (what almost all boards out there are doing) sounds > like a non-sustainable way for Qemu. > Why? As long as it Just Works, I don't think it will ever even cross a users mind. >> We'll be stuck with legacy option roms for a long, long time. But I >> also expect there will be a few devices out there that only provide >> EFI modules. >> > > I expect that it will be some time before we see such devices (maybe > only at trade show demos if at all). It will start to get interesting > once such EFI modules have to interact with classic option ROMs. > I think at the high end, we'll see these sooner than you think. Regards, Anthony Liguori