From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <lersek@redhat.com>
Received-SPF: Pass (sender SPF authorized) identity=mailfrom;
 client-ip=209.132.183.28; helo=mx1.redhat.com; envelope-from=lersek@redhat.com;
 receiver=edk2-devel@lists.01.org 
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ml01.01.org (Postfix) with ESMTPS id 9C56B21A143EF
 for <edk2-devel@lists.01.org>; Sun, 25 Nov 2018 02:22:37 -0800 (PST)
Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com
 [10.5.11.22])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.redhat.com (Postfix) with ESMTPS id 281C3C0587FC;
 Sun, 25 Nov 2018 10:22:37 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-120-51.rdu2.redhat.com
 [10.10.120.51])
 by smtp.corp.redhat.com (Postfix) with ESMTP id 729DB1054FD3;
 Sun, 25 Nov 2018 10:22:36 +0000 (UTC)
To: Peter Wiehe <peter.wiehe2@gmail.com>, edk2-devel@lists.01.org
References: <CAJzXLLwtSOO0wvpETXbiyKaYs+RkLumV3oWO4mvNZMDL6DSvjw@mail.gmail.com>
From: Laszlo Ersek <lersek@redhat.com>
Message-ID: <a4e512b0-f63e-8603-8f5b-2273291d7c71@redhat.com>
Date: Sun, 25 Nov 2018 11:22:35 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CAJzXLLwtSOO0wvpETXbiyKaYs+RkLumV3oWO4mvNZMDL6DSvjw@mail.gmail.com>
X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16
 (mx1.redhat.com [10.5.110.32]); Sun, 25 Nov 2018 10:22:37 +0000 (UTC)
Subject: Re: Structure of Tianocore?
X-BeenThere: edk2-devel@lists.01.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: EDK II Development  <edk2-devel.lists.01.org>
List-Unsubscribe: <https://lists.01.org/mailman/options/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=unsubscribe>
List-Archive: <http://lists.01.org/pipermail/edk2-devel/>
List-Post: <mailto:edk2-devel@lists.01.org>
List-Help: <mailto:edk2-devel-request@lists.01.org?subject=help>
List-Subscribe: <https://lists.01.org/mailman/listinfo/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Nov 2018 10:22:37 -0000
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit

On 11/24/18 17:41, Peter Wiehe wrote:
> I have a question for understanding the Tianocore structure:
> 
> Correct me, please, if something of the following assumptions is wrong.
> 
> a) EmulatorPkg and the Unix and Win32 (Nt32Pkg) package run ontop of an OS.
> 
> b) Ovmf runs ontop of Qemu.
> 
> c) There is a package which runs ontop of coreboot or SeaBios which can be
> run (theoretically) ontop of real hardware and Qemu. On Qemu it is slow, of
> course. On real hardware you have to flash the Bios and Uefi which, of
> course, can screw up your computer.
> 
> Which would be the package mentioned in c)?

AIUI, coreboot payload support is provided in the Coreboot*Pkg packages.
I've never tried them, but I suspect the tianocore wiki has some
articles on them.

The other package (for running UEFI on top of traditional BIOS, on a
physical machine) is DuetPkg. It's being removed:

https://bugzilla.tianocore.org/show_bug.cgi?id=1322

Thanks
Laszlo