From: Ken Goldman <kgoldman-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH 2/2] TPM2.0:Adds securityfs support for TPM2.0 eventlog
Date: Mon, 29 Aug 2016 08:52:59 -0400 [thread overview]
Message-ID: <nq1b79$kkn$1@blaine.gmane.org> (raw)
In-Reply-To: <20160729171428.GB6331-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
On 7/29/2016 1:14 PM, Jason Gunthorpe wrote:
>
> The bios log is defined to be host endian?
>
> Please reference the standard in a comment that these structs are
> coming from.
The BIOS log is little endian. That is, all multi-byte values are
little endian. Examples are the pcrIndex, eventType, and eventSize,
as well as the digest count and hashAlg.
From the "TCG PC Client Platform Firmware Profile Specification"
1.7 Specification Conventions
1. All constants and data SHALL be represented as Little Endian format
unless otherwise explicitly stated.
------------------------------------------------------------------------------
next prev parent reply other threads:[~2016-08-29 12:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 6:44 [PATCH 0/2] Cover Letter - TPM2.0: Add securityfs support for Nayna Jain
[not found] ` <1469774679-25232-1-git-send-email-nayna-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2016-07-29 6:44 ` [PATCH 1/2] TPM2.0: Refactor eventlog init functions for TPM1.2 and Nayna Jain
[not found] ` <1469774679-25232-2-git-send-email-nayna-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2016-07-29 16:57 ` Jason Gunthorpe
[not found] ` <20160729165708.GA6331-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-08-01 16:47 ` Nayna
2016-07-29 6:44 ` [PATCH 2/2] TPM2.0:Adds securityfs support for TPM2.0 eventlog Nayna Jain
[not found] ` <1469774679-25232-3-git-send-email-nayna-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2016-07-29 17:14 ` Jason Gunthorpe
[not found] ` <20160729171428.GB6331-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-08-29 12:52 ` Ken Goldman [this message]
2016-08-29 17:16 ` Jason Gunthorpe
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='nq1b79$kkn$1@blaine.gmane.org' \
--to=kgoldman-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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;
as well as URLs for NNTP newsgroup(s).