commit | 7180029213c1bb362076901bcafb22a620828613 | [log] [tgz] |
---|---|---|
author | Philip Tricca <flihp@twobit.us> | Tue Jun 21 05:02:17 2016 -0700 |
committer | Philip Tricca <philip.b.tricca@intel.com> | Tue Jul 12 19:57:02 2016 -0700 |
tree | 75e17ec4060d4d4c6d4347264a06af7826d5fe3d | |
parent | c31b087fb6f2fdd7d870be24fb2c20e95943d084 [diff] |
getcommands: Remove use of malloc function pointer. This function is only called from the resourcemgr so we really only ever need the RM specific function pointer. Further, we have no use case to provide a different allocation function in the RM so this only complicates the build and makes the code more difficult to read. Likely this was inteded to be a "future proofing" mechanism in the event that the RM would be built on systems with different allocation mechanisms? Signed-off-by: Philip Tricca <flihp@twobit.us>
This stack consists of the following layers from top to bottom:
Since the FAPI and ESAPI haven't been implemented yet, this repository only contains the SAPI and layers below it, plus a test application for exercising the SAPI.
The test application, tpmclient, tests many of the commands against the TPM 2.0 simulator. The tpmclient application can be altered and used as a sandbox to test and develop any TPM 2.0 command sequences, and provides an excellent development and learning vehicle.
TPM 2.0 specifications can be found at Trusted Computing Group.