From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: Capsule PCI device firmware update, could capsule embedded driver override PCI option ROM driver?
To: devel@edk2.groups.io
From: "Lin, Derek (HPS SW)" <derek.lin2@hpe.com>
X-Originating-Location: Singapore, SG (15.211.153.74)
X-Originating-Platform: Windows Chrome 75
User-Agent: GROUPS.IO Web Poster
MIME-Version: 1.0
Date: Thu, 08 Aug 2019 01:27:04 -0700
Message-ID: <10206.1565252824023648157@groups.io>
Content-Type: multipart/alternative; boundary="GGSjpw5iAwy7xjLxsr1P"

--GGSjpw5iAwy7xjLxsr1P
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi,

I have searched EDK2 devel discussion and Mantis but I couldn't find answe=
r.

Recently we found some PCI card vendor release capsule to update device fi=
rmware.

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

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 disconnec=
t 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 con=
nect new driver from capsule.
It makes sense for device vendor to simply provide a device driver in caps=
ule.

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

Thanks,
Derek

--GGSjpw5iAwy7xjLxsr1P
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi,<br /><br />I have searched EDK2 devel discussion and Mantis but I could=
n't find answer.<br /><br /><br />Recently we found some PCI card vendor re=
lease capsule to update device firmware.<br /><br />Background:<br />The PC=
I card has option ROM which provide FMP service.<br />The capsule has a fir=
mware payload and device driver which also provide FMP.<br /><br />Problem:=
<br />The vendor put option ROM device driver into capsule, the only differ=
ences is it is newer version.<br />The FMP in old PCI option ROM is not fun=
ctional.<br />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 caps=
ule.<br /><br />This is different to current EDK2 implementation. UEFI spec=
 2.8 CH 23.3.3 define process to handle capsule and embedded driver, it wil=
l call embedded driver's entry point, but won't connect anything.<br /><br =
/>Our PCI card vendor is asking to disconnect old option ROM driver, and co=
nnect new driver from capsule.<br />It makes sense for device vendor to sim=
ply provide a device driver in capsule.<br /><br /><br />Any advice? Do you=
 think it make sense to disconnect PCI option ROM driver and reconnect caps=
ule driver?<br /><br />Thanks,<br />Derek

--GGSjpw5iAwy7xjLxsr1P--