[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [coreboot] [Qemu-devel] Release plan for 0.12.0

From: Carl-Daniel Hailfinger
Subject: Re: [coreboot] [Qemu-devel] Release plan for 0.12.0
Date: Mon, 05 Oct 2009 15:23:27 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20081213 SUSE/1.1.14-1.1 SeaMonkey/1.1.14

On 05.10.2009 15:03, Anthony Liguori wrote:
> Stefan Reinauer wrote:
>> 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?
> We'll I've been advocating UEFI + CSM (based on SeaBIOS) so I'm not
> sure what you meant by 'that road'.

What about SeaBIOS + CSM (based on DUET)? That allows you to continue
using all the Qemu specific init code in SeaBIOS and optionally load
UEFI if some hardware needs it.
A SeaBIOS based CSM will probably never get merged/supported at
tianocore.org because of licensing, but the SeaBIOS + DUET solution
should be supportable by upstream.

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.

>> 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.
> 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.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]