test/unit/tcti-device.c: fix unit test fail on armel, armhf, mipsel

Inside the teardown function, it converts a pointer to wrong type.
This commit fixes the bug.

Signed-off-by: Ying-Chun Liu (PaulLiu) <paulliu@debian.org>
1 file changed
tree: 0912b2e73a8ef899c3c17d00b3e5ff7993a69d94
  1. common/
  2. doc/
  3. include/
  4. lib/
  5. m4/
  6. man/
  7. script/
  8. sysapi/
  9. tcti/
  10. test/
  11. .gitattributes
  12. .gitignore
  13. .travis.yml
  14. AUTHORS
  15. bootstrap
  16. CHANGELOG.md
  17. configure.ac
  18. CONTRIBUTING.md
  19. INSTALL
  20. LICENSE
  21. MAINTAINERS
  22. Makefile.am
  23. README.md
  24. RELEASE.md
README.md

Build Status Coverity Scan

TPM (Trusted Platform Module) 2.0 Software Stack (TSS):

This stack consists of the following layers from top to bottom:

  • Feature API (FAPI), see specification 0.12, (published but still in progress and unimplemented)
  • Enhanced System API (ESAPI), (specification in progress and unimplemented)
  • System API (SAPI), see 1.0 specification, (public, 0.97 implementation complete). This layer implements the system layer API level of the TSS 2.0 specification. These functions can be used to access all TPM 2.0 functions as described in Part 3 of the TPM 2.0 specification. The usefulness of this code extends to all users of the TPM, even those not planning to use the upper layers of the TSS.
  • TPM Command Transmission Interface (TCTI), used by SAPI to communicate with next lower layer (either the TAB/RM or TPM 2.0 device driver), see SAPI specification
  • Trusted Access Broker/Resource Manager (TAB/RM), see 0.91 specification, (public, implementation complete). This layer sits between the system API library code and the TPM. It is a daemon that handles all multi-process coordination and manages the TPM's internal resources transparently to applications.

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.

Build and Installation Instructions:

Run Instructions

Architecture/Block Diagram

Code Layout

Resources

TPM 2.0 specifications can be found at Trusted Computing Group.