From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Peter Huewe <peterhuewe@gmx.de>,
tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [tpmdd-devel] [PATCH] tpm: Add sysfs interface to show TPM hardware version
Date: Wed, 15 Mar 2017 11:25:56 -0600 [thread overview]
Message-ID: <20170315172556.GA6399@obsidianresearch.com> (raw)
In-Reply-To: <1489527771.19081.49.camel@HansenPartnership.com>
On Tue, Mar 14, 2017 at 02:42:51PM -0700, James Bottomley wrote:
> On Tue, 2017-03-14 at 15:24 -0600, Jason Gunthorpe wrote:
> > On Tue, Mar 14, 2017 at 07:58:37PM +0100, Peter Huewe wrote:
> >
> > > > In practice, I suspect that a single user space application won't
> > > > support both TPMs.
> > > Think of init scripts.
> > > Which daemon should it start?
> >
> > Right, ideally we'd have a udev rule that triggers systemd to start
> > the userspace daemons when a TPM is detected, as other hardware does.
> >
> > So whatever format we use has to be compatible with udev's matcher..
>
> Technically, we have that already: my TPM2.0 detection stuff for udev
> triggers off the presence of the SUBSYSTEM=="tpmrm" that matches any
> TPM2 device but not a 1.x one.
but long term tpmrm won't be TPM2 exclusive..
Jason
next prev parent reply other threads:[~2017-03-15 17:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 5:21 [PATCH] tpm: Add sysfs interface to show TPM hardware version Meng.Li
2017-03-13 5:21 ` Meng.Li
[not found] ` <1489382517-9078-1-git-send-email-Meng.Li-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org>
2017-03-13 7:10 ` Peter Huewe
2017-03-13 7:10 ` Peter Huewe
2017-03-13 7:47 ` Li, Meng
2017-03-14 18:18 ` [tpmdd-devel] " Ken Goldman
[not found] ` <9f67321b-50bd-9e6f-61f8-c29ae14f261f-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-03-14 18:58 ` Peter Huewe
2017-03-14 18:58 ` [tpmdd-devel] " Peter Huewe
[not found] ` <074515F2-51E7-485B-B1AB-11B913CC4B46-Mmb7MZpHnFY@public.gmane.org>
2017-03-14 21:24 ` Jason Gunthorpe
2017-03-14 21:24 ` [tpmdd-devel] " Jason Gunthorpe
[not found] ` <20170314212425.GA29359-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-03-14 21:42 ` James Bottomley
2017-03-14 21:42 ` [tpmdd-devel] " James Bottomley
2017-03-15 17:25 ` Jason Gunthorpe [this message]
2017-03-13 11:48 ` Jarkko Sakkinen
[not found] ` <20170313114852.kmfequmchxi3jams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-03-13 12:37 ` Li, Meng
2017-03-13 12:37 ` Li, Meng
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=20170315172556.GA6399@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=tpmdd-devel@lists.sourceforge.net \
/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.