From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] [PATCH v1 1/1] FmpDevicePkg: FmpDeviceLib interface change for Driver Unload support To: John Rahn ,devel@edk2.groups.io From: gordontcp@gmail.com X-Originating-Location: Hsinchu, TW (61.222.87.235) X-Originating-Platform: Windows Chrome 103 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Fri, 22 Jul 2022 03:02:11 -0700 References: In-Reply-To: Message-ID: <3602.1658484131194749573@groups.io> Content-Type: multipart/alternative; boundary="MOTFRGaxqpgguW0jfDm0" --MOTFRGaxqpgguW0jfDm0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, I would like to handle =E2=80=98DriverBinding protocol=E2=80=99 model in = =E2=80=98RegisterFmpInstaller=E2=80=99 to get control of USBIO. Since there= is no corresponding example for EDK2, this part is not easy to implement. = Can you provide an example of how RegisterFmpInstaller handles the DriverBi= nding protocol, so as to facilitate the realization of the function of FMPD= xe update capsule. Any suggestion is highly appreciated. Thanks! --MOTFRGaxqpgguW0jfDm0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Hi,

I would like to handle = =E2=80=98DriverBinding protocol=E2=80=99 model in =E2=80=98RegisterFmpInsta= ller=E2=80=99 to get control of USBIO. Since there is no corresponding exam= ple for EDK2, this part is not easy to implement. Can you provide an exampl= e of how RegisterFmpInstaller handles the DriverBinding protocol, so as to = facilitate the realization of the function of FMPDxe update capsule.=

Any suggestion is highly= appreciated.

Thanks!

--MOTFRGaxqpgguW0jfDm0--