Hi Derek: Can you specify the "reversed" ManufactureId issue? What did you get from this interface? The implementation follows Vendor ID registry spec. The vendor ID is octet array. There is no endian issue here. We haven't seen any disorder before.
From: Lin, Derek (HPS UEFI Dev) [mailto:derek.l...@hpe.com] Sent: Thursday, February 22, 2018 7:25 PM To: firstname.lastname@example.org; Zhang, Chao B <chao.b.zh...@intel.com> Cc: Yao, Jiewen <jiewen....@intel.com>; Zeng, Star <star.z...@intel.com> Subject: TPM 2.0 Manufacutre ID wrong byte order Hi TPM expert, The line in https://github.com/tianocore/edk2/commit/73126ac2bd9804632255b2fddd4d7633537c9620#diff-76abe1c1ebf05982ed72eaf56f489029R192 change the byte order of Manufacture ID in Tpm2GetCapabilityManufactureID (). I see it return "reversed" ManufactureId for two TPM vendor's module. Also, all other Capability data in Tpm2Capability.c use SwapBytes32 since TPM is big-endian, which seems correct. Can you check this and confirm? Thanks, Derek _______________________________________________ edk2-devel mailing list email@example.com https://lists.01.org/mailman/listinfo/edk2-devel