public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: "Tomas Pilar (tpilar)" <tpilar@solarflare.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Gao, Liming" <liming.gao@intel.com>
Subject: Re: FmpDeviceLib
Date: Tue, 27 Nov 2018 14:33:59 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E373119@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <3d05d3db-1a45-99f7-95ac-5bc77daf0494@solarflare.com>

Tom:
  FmpDeviceLib can use UEFI driver model/driver binding protocol so it can install FMP on its device handle during the BDS/Device connection phase. It can implement RegisterFmpInstaller() to install FMP protocol in its device handle. In this way, FmpDeviceLib is like UEFI driver with UEFI driver binding protocol. 

Thanks
Liming
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@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 instance when calling the library functions, leading me to believe that the only way to do this is to assign a pointer to
> private struct during library construction, but that means that a driver that uses the code can only ever service a single controller.
> 
> Can you offer any insights?
> 
> Cheers,
> Tom
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2018-11-27 14:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 13:25 FmpDeviceLib Tomas Pilar (tpilar)
2018-11-27 14:33 ` Gao, Liming [this message]
2018-11-27 15:23   ` FmpDeviceLib Tomas Pilar (tpilar)
2018-11-27 15:28     ` FmpDeviceLib Tomas Pilar (tpilar)
2018-11-28  1:15       ` FmpDeviceLib Kinney, Michael D
2018-11-28 10:43         ` FmpDeviceLib Tomas Pilar (tpilar)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A89E2EF3DFEDB4C8BFDE51014F606A14E373119@SHSMSX104.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox