From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mtapq-0007pN-0v for qemu-devel@nongnu.org; Fri, 02 Oct 2009 01:37:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mtapk-0007pB-ED for qemu-devel@nongnu.org; Fri, 02 Oct 2009 01:37:40 -0400 Received: from [199.232.76.173] (port=53866 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mtapk-0007p8-8F for qemu-devel@nongnu.org; Fri, 02 Oct 2009 01:37:36 -0400 Received: from mx20.gnu.org ([199.232.41.8]:34098) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mtapj-0008Oy-OI for qemu-devel@nongnu.org; Fri, 02 Oct 2009 01:37:35 -0400 Received: from mail-yx0-f173.google.com ([209.85.210.173]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mtapj-0005Fj-2E for qemu-devel@nongnu.org; Fri, 02 Oct 2009 01:37:35 -0400 Received: by yxe3 with SMTP id 3so803162yxe.4 for ; Thu, 01 Oct 2009 22:37:34 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1CD2353A-CCE0-4E2C-B3A7-9E6D2E9D34C7@claunia.com> References: <4AC29E4D.80707@us.ibm.com> <4AC46327.4030004@gmx.net> <1CD2353A-CCE0-4E2C-B3A7-9E6D2E9D34C7@claunia.com> Date: Thu, 1 Oct 2009 22:37:33 -0700 Message-ID: <2a50f7880910012237g3667a5b2sc08193829adc3f73@mail.gmail.com> Subject: Re: [Qemu-devel] Release plan for 0.12.0 From: Jordan Justen Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Natalia Portillo Cc: Carl-Daniel Hailfinger , qemu-devel@nongnu.org I work for Intel on the edk2.tianocore.org project.=A0 (Compared to the original edk) edk2 may be of interest to those on this list since it supports building on several OS's with several different toolchains. In other words, it also supports building under Linux and OS X with the GNU compiler and binutils. Within our edk2 tree, we have two projects that relate to QEMU. The DUET platform is a UEFI emulator that boots like a legacy OS on top of a legacy BIOS.=A0 It contains various hardware initialization drivers for several legacy hardware devices, but it also will call into the legacy BIOS and make use of certain items from the legacy BIOS.=A0 DUET can boot from the QEMU legacy BIOS, but it does require a disk to be setup to have the DUET image on it.=A0 I am not sure if all of DUET's code is currently safe for a UEFI OS to be able to access UEFI runtime services. The OVMF platform is a project to build a (mostly) UEFI compatible firmware for virtual machines.=A0 QEMU support is one of the main goals for OVMF.=A0 The OVMF rom image completely replaces QEMU's standard bios.bin, and therefore we must have hardware drivers for any hardware within the QEMU VM that we want to make use of. The project also has the goal to support UEFI OS's at runtime. -Jordan On Thu, Oct 1, 2009 at 21:38, Natalia Portillo wrote: > > The only opensource EFI implementation I know about is the Intel EFI Refe= rence. > > Dunno if it includes hardware initialization. > > El 01/10/2009, a las 09:07, Carl-Daniel Hailfinger escribi=F3: > >> On 01.10.2009 03:55, Natalia Portillo wrote: >>> >>> for target-i386 and target-x86_64: >>> >>> o EFI firmware emulation (as a machine or command line option) >> >> Are there any opensource EFI implementations with hardware init? I know >> that an opensource EFI glue layer exists, but AFAIK hardware init is >> still closed source. That leaves coreboot+UEFI (works somewhat) or >> SeaBIOS+UEFI (no idea if this is possible). If I missed an announcement >> about opensource hw init for EFI, I wish to apologize. >> >> Regards, >> Carl-Daniel >> >> -- >> http://www.hailfinger.org/ >> >> > > >