From: Sasha Levin <sashal@kernel.org>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: peterhuewe@gmx.de, jarkko.sakkinen@linux.intel.com, jgg@ziepe.ca,
corbet@lwn.net, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-kernel@microsoft.com, thiruan@microsoft.com,
bryankel@microsoft.com
Subject: Re: [PATCH v3 2/2] ftpm: add documentation for ftpm driver
Date: Wed, 17 Apr 2019 13:26:28 -0400 [thread overview]
Message-ID: <20190417172628.GF435@sasha-vm> (raw)
In-Reply-To: <b2c1b45e-515d-1d91-e3d9-5f9078078cae@metux.net>
On Wed, Apr 17, 2019 at 02:23:13PM +0200, Enrico Weigelt, metux IT consult wrote:
>On 15.04.19 17:56, Sasha Levin wrote:
>
>Hi,
>
>> +The driver acts as a thin layer that passes commands to and from a TPM> +implemented in firmware. The driver itself doesn't contain much logic
>and is> +used more like a dumb pipe between firmware and kernel/userspace.
>Is that TPM already used in production or yet an PoC ?
>IOW: can the protocol be changed ?
Sadly no, this is based on something that exists for a few years already
and we're trying to make Linux run on it.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-04-17 17:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 15:56 [PATCH v3 0/2] ftpm: a firmware based TPM driver Sasha Levin
2019-04-15 15:56 ` [PATCH v3 1/2] ftpm: firmware TPM running in TEE Sasha Levin
2019-05-15 8:12 ` Jarkko Sakkinen
2019-05-17 13:22 ` Sasha Levin
2019-05-20 11:58 ` Jarkko Sakkinen
2019-05-20 15:30 ` Igor Opaniuk
2019-04-15 15:56 ` [PATCH v3 2/2] ftpm: add documentation for ftpm driver Sasha Levin
2019-04-17 12:23 ` Enrico Weigelt, metux IT consult
2019-04-17 17:26 ` Sasha Levin [this message]
2019-05-15 8:14 ` Jarkko Sakkinen
2019-05-07 17:40 ` [PATCH v3 0/2] ftpm: a firmware based TPM driver Sasha Levin
2019-05-08 4:41 ` Sumit Garg
2019-05-08 8:02 ` Daniel Thompson
2019-05-08 8:24 ` Sumit Garg
2019-05-08 12:44 ` Jarkko Sakkinen
2019-05-14 19:30 ` Sasha Levin
2019-05-15 2:02 ` Sumit Garg
2019-05-16 1:00 ` Thirupathaiah Annapureddy
2019-05-16 7:06 ` Sumit Garg
2019-05-16 19:24 ` Thirupathaiah Annapureddy
2019-05-17 6:57 ` Sumit Garg
2019-05-17 17:23 ` Thirupathaiah Annapureddy
2019-05-19 9:46 ` Sumit Garg
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=20190417172628.GF435@sasha-vm \
--to=sashal@kernel.org \
--cc=bryankel@microsoft.com \
--cc=corbet@lwn.net \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=peterhuewe@gmx.de \
--cc=thiruan@microsoft.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.