On 06/26/19 13:43, David Woodhouse wrote:
> 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?

Yes, it can be turned off. It is a common hiccup for new subscribers
(the groups.io default is broken). I think we meant to document it
somewhere (outside of the mailing list archive), and I guess we may have
even done so, but currently a non-list reference escapes me.

Anyway, please see the attached messages -- and then please log in to
your groups.io account, locate

  Account
    Preferences
      Email Preferences
        My Posts
          I always want copies of my own emails

and *uncheck* it.

Because, in reality, that checkbox stands for "munge my Message-IDs so
that GMail doesn't de-duplicate my own emails when the list reflects
them to me". But, two wrongs don't make a right :/

Thanks,
Laszlo

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