7:29 AM
>> To: Gao, Liming ; edk2-
>> de...@lists.01.org
>> Subject: Re: [edk2] FmpDeviceLib
>>
>> Okay, so I just noticed that FmpDxe is full of module
>> globals including the image descriptor, so it
>> necessarily requires that the driver that includes it a
1.org] On Behalf Of Tomas Pilar (tpilar)
> Sent: Tuesday, November 27, 2018 7:29 AM
> To: Gao, Liming ; edk2-
> de...@lists.01.org
> Subject: Re: [edk2] FmpDeviceLib
>
> Okay, so I just noticed that FmpDxe is full of module
> globals including the image descriptor, so it
&
t;>> -Original Message-
>>> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
>>> Tomas Pilar (tpilar)
>>> Sent: Tuesday, November 27, 2018 9:26 PM
>>> To: edk2-devel@lists.01.org
>>> Subject: [edk2] FmpDeviceLib
>
tpilar)
>> Sent: Tuesday, November 27, 2018 9:26 PM
>> To: edk2-devel@lists.01.org
>> Subject: [edk2] FmpDeviceLib
>>
>> Hi all,
>>
>> I am looking at using FmpDxeLib so I need to implement the FmpDeviceLib.
>> However, it seems like the library fun
driver binding
protocol.
Thanks
Liming
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Tomas
> Pilar (tpilar)
> Sent: Tuesday, November 27, 2018 9:26 PM
> To: edk2-devel@lists.01.org
> Subject: [edk2] FmpDeviceLib
>
Hi all,
I am looking at using FmpDxeLib so I need to implement the FmpDeviceLib.
However, it seems like the library functions do not take any private struct as
a parameter, so I am struggling to figure out how to read information off the
hardware. FmpDxe does not even pass its created protocol
6 matches
Mail list logo
