From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MuChD-0004c8-5R for qemu-devel@nongnu.org; Sat, 03 Oct 2009 18:03:19 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MuCh7-0004XY-Ly for qemu-devel@nongnu.org; Sat, 03 Oct 2009 18:03:18 -0400 Received: from [199.232.76.173] (port=56510 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MuCh7-0004XP-Ix for qemu-devel@nongnu.org; Sat, 03 Oct 2009 18:03:13 -0400 Received: from ra.coresystems.de ([80.81.252.129]:43633) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MuCh6-00066A-VD for qemu-devel@nongnu.org; Sat, 03 Oct 2009 18:03:13 -0400 Message-ID: <4AC7CA13.1090007@coresystems.de> Date: Sun, 04 Oct 2009 00:02:59 +0200 From: Stefan Reinauer 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> In-Reply-To: <2a50f7880910031449k13090dcdr8440d89ccb7fcfe9@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jordan Justen Cc: ron minnich , Anthony Liguori , Coreboot , Carl-Daniel Hailfinger , qemu-devel@nongnu.org Jordan Justen wrote: > On Sat, Oct 3, 2009 at 10:30, Peter Stuge wrote: > >> Jordan Justen wrote: >> >>> Anyway, it sounds like a useful project might be to develop a UEFI >>> coreboot payload based on the tianocore.org code. >>> >> I believe it might have been done already. >> >> http://www.coreboot.org/File:Tianocoreboot.png >> > > That screenshot mentions DUET which is the tianocore.org UEFI emulator > that boots on top of a legacy BIOS. But, it's unclear if it was just > DUET, or something based modified specifically for coreboot based on > DUET. > > I will not dispute that DUET might be a potential solution to achieve > UEFI compatibility for QEMU. (I'm not sure, but I think DUET may not > be able to boot UEFI OS's at this time.) However, we thought a > project such as OVMF was a more direct approach to achieve UEFI > compatibility for QEMU. > We have DUET running as a coreboot payload with a small coreboot specific PE payload loader. DUET is, however, not an emulator, it is executing much of the same code as all other TianoCore based UEFI implementations. It is possible to boot an OS just fine with DUET. Can you explain what you think would be more direct about OVMF than about DUET? As far as I understand it's another build target of EDK2 but besides that shares exactly the same design and even 99% of the code. Stefan -- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info@coresystems.de • http://www.coresystems.de/ Registergericht: Amtsgericht Freiburg • HRB 7656 Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866