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.