commit | 45fb1093e91b6a286dd87423811e32d9367993a4 | [log] [tgz] |
---|---|---|
author | Gang Wei <gang.wei@intel.com> | Sat Apr 23 01:22:43 2016 +0800 |
committer | Philip Tricca <philip.b.tricca@intel.com> | Fri Apr 22 15:48:53 2016 -0400 |
tree | 045218c4f9cd80c00c283095cae20c572b054f10 | |
parent | 4f2bdd7fa931e17ee04c4096c2ad355d4704d7af [diff] |
RM: Only send 'PlatformCommand' to simulator. When the RM receives a platform command from clients it should only proxy them along to the TPM if it's the simulator. These commands are specific to the simulator after all. We do however need to respond to the application even if the command is being dropped. When we do drop a platform command we now respond with a value indicating success. In the RM initialization code there were a few places where it was attmepting to invoke PlatformCommand even if it wasn't communicating with the simulator. These calls have placed within a check for the 'simulator' flag. Signed-off-by: Philip Tricca <philip.b.tricca@intel.com>
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.