From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: Sergei Temerkhanov <s.temerkhanov@gmail.com>,
"Tomas Pilar (tpilar)" <tpilar@solarflare.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Reusing DXE driver code in edk2 packages
Date: Wed, 17 May 2017 15:41:06 +0000 [thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F57D174F34@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <CAPEA6dY6OqyO5QL3fadUcTLVn14KaqTCy6e7kXwjJsK6KDxhbg@mail.gmail.com>
Sergey,
For a UEFI driver, you can look for the Time Stamp Protocol. If it
is present, you can use it. This is an optional protocol, so a UEFI
driver must continue to work if the protocol is not provided by the
platform firmware. The UEFI driver should fall back to other UEFI
spec defined time sources or reduce features if those time sources
are not sufficient.
Mike
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Sergei
> Temerkhanov
> Sent: Wednesday, May 17, 2017 7:44 AM
> To: Tomas Pilar (tpilar) <tpilar@solarflare.com>
> Cc: edk2-devel@lists.01.org
> Subject: Re: [edk2] Reusing DXE driver code in edk2 packages
>
> On Wed, May 17, 2017 at 5:18 PM, Tomas Pilar (tpilar)
> <tpilar@solarflare.com> wrote:
> > Hi,
> >
> > I want to use timestamping in my optionrom UEFI driver so I checkout the
> > Timestamp protocol that comes in UEFI 2.5. I check my platform for
> > gEfiTimestampProtocolGuid using gBS->LocateProtocol but that comes up empty.
> >
> > In EDK2 I notice MdeModulePkg/Universal/TimestampDxe which is a DXE driver
> > that uses TimerLib to produce timestamps. How would I use this in my driver?
> > Can I just stick the TimestampDxe.inf as a library to [LibraryClasses] in my
> > package DSC file?
>
> TimestampDxe.inf goes into the [Components] section, and into the .fdf
> file as well.
> Also, [Depex] sections of modules using this protocol have to contain
> gEfiTimestampProtocolGuid.
>
> Regards,
> Sergey
>
> >
> > Cheers,
> > Tom
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org
> > https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-05-17 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 14:18 Reusing DXE driver code in edk2 packages Tomas Pilar (tpilar)
2017-05-17 14:31 ` Gao, Liming
2017-05-17 14:44 ` Sergei Temerkhanov
2017-05-17 15:41 ` Kinney, Michael D [this message]
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=E92EE9817A31E24EB0585FDF735412F57D174F34@ORSMSX113.amr.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