From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MuWvu-0001GV-2e
	for qemu-devel@nongnu.org; Sun, 04 Oct 2009 15:39:50 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MuWvp-0001F0-EY
	for qemu-devel@nongnu.org; Sun, 04 Oct 2009 15:39:49 -0400
Received: from [199.232.76.173] (port=45595 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MuWvp-0001Ex-7X
	for qemu-devel@nongnu.org; Sun, 04 Oct 2009 15:39:45 -0400
Received: from ra.coresystems.de ([80.81.252.129]:48969)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <stepan@coresystems.de>) id 1MuWvo-0000eU-PR
	for qemu-devel@nongnu.org; Sun, 04 Oct 2009 15:39:45 -0400
Message-ID: <4AC8F9F2.3030508@coresystems.de>
Date: Sun, 04 Oct 2009 21:39:30 +0200
From: Stefan Reinauer <stepan@coresystems.de>
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>
In-Reply-To: <4AC8F80C.2050702@us.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Coreboot <coreboot@coreboot.org>, qemu-devel@nongnu.org, Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>, ron minnich <rminnich@gmail.com>, Jordan Justen <jljusten@gmail.com>, Patrick Georgi <patrick@georgi-clan.de>

Anthony Liguori wrote:
> Patrick Georgi wrote:
>> With coreboot, seabios and Duet, it should be reasonably simple to
>> provide a single BIOS image that selects (based on nvram - ie.
>> configuration) which interface to provide: PCBIOS or UEFI.
>>   
>
> That isn't terribly useful for QEMU because it implies that QEMU needs
> to make the decision about which one to use.  If QEMU was capable of
> making that decision without user intervention, then we could just
> select to load PCBIOS or UEFI.
Are you guys sure you want to go down that road rather than using an
UEFI with a CSM? There may be cases when you really want to boot legacy
even though your client can do UEFI.

> I don't know enough about EFI, but my concern is that down the road,
> hardware devices will start to exist that require EFI because they
> implement EFI modules and not legacy option ROMs.  In order to support
> PCI passthrough of such devices, we will need to provide an EFI
> capable firmware.
>
> It's really just a matter of how long before this becomes a problem
> for us.
This was attempted for Open Firmware and never happened during its life
time. I doubt there is any incentive for vendors to ship devices without
legacy option roms, especially since there is no advantage in doing so.

Stefan