Capsule PCI device firmware update, could capsule embedded driver override PCI option ROM driver?

["Lin, Derek (HPS SW)" <derek.lin2@hpe.com>]

[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]

Hi,

I have searched EDK2 devel discussion and Mantis but I couldn't find answer.

Recently we found some PCI card vendor release capsule to update device firmware.

Background:
The PCI card has option ROM which provide FMP service.
The capsule has a firmware payload and device driver which also provide FMP.

Problem:
The vendor put option ROM device driver into capsule, the only differences is it is newer version.
The FMP in old PCI option ROM is not functional.
Thus they put a new device driver in capsule, and expect UEFI to disconnect the old option ROM driver, and connect the new one from capsule.

This is different to current EDK2 implementation. UEFI spec 2.8 CH 23.3.3 define process to handle capsule and embedded driver, it will call embedded driver's entry point, but won't connect anything.

Our PCI card vendor is asking to disconnect old option ROM driver, and connect new driver from capsule.
It makes sense for device vendor to simply provide a device driver in capsule.

Any advice? Do you think it make sense to disconnect PCI option ROM driver and reconnect capsule driver?

Thanks,
Derek

[-- Attachment #2: Type: text/html, Size: 1243 bytes --]