From: "David Woodhouse" <dwmw2@infradead.org>
To: devel@edk2.groups.io, ray.ni@intel.com,
"lersek@redhat.com" <lersek@redhat.com>
Subject: Re: [edk2-devel] [PATCH 6/7] MdeModulePkg/UefiBootManagerLib: describe VirtIO devices correctly
Date: Tue, 25 Jun 2019 10:28:49 +0100 [thread overview]
Message-ID: <cc0fcec1f6ecc79483e52a30587d33faa95a2445.camel@infradead.org> (raw)
In-Reply-To: <734D49CCEBEEF84792F5B80ED585239D5C1EF35C@SHSMSX104.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 433 bytes --]
On Tue, 2019-06-25 at 09:15 +0000, Ni, Ray wrote:
> But I still need to understand why the *GetBootOption() API is needed.
> Because for quite a long time since the MdeModulePkg/Bds was added, there is no
> such requirement.
It's for CSM, because otherwise all the legacy boot targets other than
IDE are just shown as 'Harddisk'.
See patch [5/7] in this thread which uses the GetBootDescription API
that [4/7] exposes.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2019-06-25 9:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 22:31 [PATCH 1/7] OvmfPkg/LegacyBios: set NumberBbsEntries to the size of BbsTable David Woodhouse
2019-06-21 22:31 ` [PATCH 2/7] OvmfPkg/LegacyBbs: Add boot entries for VirtIO and NVME devices David Woodhouse
2019-06-24 22:46 ` [edk2-devel] " Laszlo Ersek
2019-06-21 22:31 ` [PATCH 3/7] OvmfPkg: Don't build in QemuVideoDxe when we have CSM David Woodhouse
2019-06-21 22:31 ` [PATCH 4/7] MdeModulePkg/UefiBootManagerLib: export EfiBootManagerGetBootDescription() David Woodhouse
2019-06-24 22:36 ` [edk2-devel] " Laszlo Ersek
2019-06-25 2:00 ` Ni, Ray
2019-06-25 8:00 ` David Woodhouse
2019-06-21 22:31 ` [PATCH 5/7] OvmfPkg/LegacyBiosDxe: Use EfiBootManagerGetBootDescription() David Woodhouse
2019-06-24 23:03 ` [edk2-devel] " Laszlo Ersek
2019-06-21 22:31 ` [PATCH 6/7] MdeModulePkg/UefiBootManagerLib: describe VirtIO devices correctly David Woodhouse
2019-06-24 23:16 ` [edk2-devel] " Laszlo Ersek
2019-06-25 1:44 ` Ni, Ray
2019-06-25 7:40 ` David Woodhouse
2019-06-25 8:06 ` Ni, Ray
2019-06-25 8:28 ` David Woodhouse
2019-06-25 9:15 ` Ni, Ray
2019-06-25 9:28 ` David Woodhouse [this message]
2019-06-25 9:56 ` Ni, Ray
2019-06-25 11:27 ` David Woodhouse
2019-06-21 22:31 ` [PATCH 7/7] OvmfPkg: don't assign PCI BARs above 4GiB when CSM enabled David Woodhouse
2019-06-24 23:50 ` [edk2-devel] " Laszlo Ersek
2019-06-25 12:07 ` David Woodhouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cc0fcec1f6ecc79483e52a30587d33faa95a2445.camel@infradead.org \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox