From: "David Woodhouse" <dwmw2@infradead.org>
To: devel@edk2.groups.io
Cc: Laszlo Ersek <lersek@redhat.com>
Subject: Re: [edk2-devel] [PATCH v3 0/4] OvmfPkg: CSM boot fixes
Date: Wed, 26 Jun 2019 12:43:57 +0100 [thread overview]
Message-ID: <536d4b904ecc507b84eaefd8c34510e72e38ec67.camel@infradead.org> (raw)
In-Reply-To: <15ABBC9A305FBCEC.16820@groups.io>
[-- Attachment #1: Type: text/plain, Size: 2082 bytes --]
On Wed, 2019-06-26 at 12:37 +0100, David Woodhouse wrote:
> For v3, leaving out the cosmetic parts that touch code outside OvmfPkg.
> This series is now purely the correctness fixes within OvmfPkg which are
> required to make CSM boots work properly again.
>
> The first two patches allow NVMe and VirtIO disks to be used as Legacy
> boot targets, since nobody really uses IDE any more.
>
> The third avoids using QemuVideoDxe when we have CSM, as the INT 10h
> shim installed by QemuVideoDxe conflicts with a real legacy video BIOS
> being installed.
>
> Finally, avoid placing PCI BARs above 4GiB. Strictly speaking we only
> need this for PCI devices which might be natively supported by the CSM
> BIOS, like NVMe. Devices with an OpRom already get special-cased to stay
> below 4GiB. But an IncompatiblePciDeviceSupportProtocol implementation
> doesn't get to see the PCI device class; only the vendor/device IDs so
> we can't use it for that purpose to downgrade more selectively. Instead,
> just default to putting everything below 4GiB.
Btw, these four patches alone are pushed to
http://git.infradead.org/users/dwmw2/edk2.git/shortlog/refs/heads/csm-ovmfpkg
But... this cover letter has been detached from the thread with the patches.
When git-send-email created them, the cover letter had
Message-Id: <20190626113742.819933-1-dwmw2@infradead.org>
All the subsequent patches had:
References: <20190626113742.819933-1-dwmw2@infradead.org>
But they all get their message-id corrupted on the way through the
list, it seems. So the References: headers in the patches are
referencing a Message-ID: that no longer exists.
Why does the list do this? Can it be turned off, please?
Or at the very least, can it be set to mangle References: and In-Reply-
To: headers to match the corruption it introduces into the Message-Id:
headers and at least keep threading intact? That still doesn't keep
things in sync with messages that *don't* go through the list though,
so fixing it not to do any corruption at all would be best.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]
next parent reply other threads:[~2019-06-26 11:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15ABBC9A305FBCEC.16820@groups.io>
2019-06-26 11:43 ` David Woodhouse [this message]
2019-06-26 12:18 ` [edk2-devel] [PATCH v3 0/4] OvmfPkg: CSM boot fixes Laszlo Ersek
2019-06-26 12:33 ` David Woodhouse
2019-06-26 12:41 ` David Woodhouse
2019-06-26 14:48 ` Laszlo Ersek
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=536d4b904ecc507b84eaefd8c34510e72e38ec67.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