All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
	Peter Huewe <peterhuewe@gmx.de>
Cc: 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: Tue, 14 Mar 2017 14:42:51 -0700	[thread overview]
Message-ID: <1489527771.19081.49.camel@HansenPartnership.com> (raw)
In-Reply-To: <20170314212425.GA29359@obsidianresearch.com>

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.

James

WARNING: multiple messages have this Message-ID (diff)
From: James Bottomley <James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
To: Jason Gunthorpe
	<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
	Peter Huewe <peterhuewe-Mmb7MZpHnFY@public.gmane.org>
Cc: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] tpm: Add sysfs interface to show TPM hardware version
Date: Tue, 14 Mar 2017 14:42:51 -0700	[thread overview]
Message-ID: <1489527771.19081.49.camel@HansenPartnership.com> (raw)
In-Reply-To: <20170314212425.GA29359-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>

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.

James



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

  reply	other threads:[~2017-03-14 21:42 UTC|newest]

Thread overview: 17+ 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
2017-03-13  7:10 ` Peter Huewe
2017-03-13  7:10   ` Peter Huewe
2017-03-13  7:47   ` Li, Meng
2017-03-13  7:47     ` Li, Meng
2017-03-14 18:18   ` [tpmdd-devel] " Ken Goldman
2017-03-14 18:58     ` Peter Huewe
2017-03-14 18:58       ` Peter Huewe
2017-03-14 21:24       ` [tpmdd-devel] " Jason Gunthorpe
2017-03-14 21:24         ` Jason Gunthorpe
2017-03-14 21:42         ` James Bottomley [this message]
2017-03-14 21:42           ` James Bottomley
2017-03-15 17:25           ` [tpmdd-devel] " Jason Gunthorpe
2017-03-13 11:48 ` Jarkko Sakkinen
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=1489527771.19081.49.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=jgunthorpe@obsidianresearch.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.