From: Tadeusz Struk <tadeusz.struk at intel.com>
To: tpm2@lists.01.org
Subject: [tpm2] Re: [tpm2]How to get the feature api implementation?
Date: Tue, 08 Oct 2019 09:33:04 -0700 [thread overview]
Message-ID: <2cf41603-2fad-a1c1-ffa6-4e205d68daf3@intel.com> (raw)
In-Reply-To: CALb=tET6EAQLHmxsByd6HezG7pjG0CVXvZjqTj-yMuPY-cgKmw@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
On 10/8/19 8:48 AM, yue peng wrote:
> I'm a freshman. Recently I'm reading some specifications and books of tpm2, and trying to compile the tpm2-tss, tpm2-tools, simulator tpm and some thing else on my linux. I noticed that the tpm2-tss has implemented the enhanced-system API and the system API, but I cannot found the feature api of tpm2 on github. I'm confused the where can I found the Feature API implemention?
> Thanks for your reply.
The FAPI implementation is in progress and a PR for it will be posted soon. Stay tuned.
You are welcome to try it and contribute changes/improvements as soon as it is available.
Thanks,
--
Tadeusz
reply other threads:[~2019-10-08 16:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-all 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=2cf41603-2fad-a1c1-ffa6-4e205d68daf3@intel.com \
--to=tpm2@lists.01.org \
/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