From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: "David R. Bild" <david.bild@xaptum.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
philip.b.tricca@intel.com, Jason Gunthorpe <jgg@ziepe.ca>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Peter Huewe <peterhuewe@gmx.de>,
linux-usb@vger.kernel.org, linux-integrity@vger.kernel.org
Subject: Re: [PATCH v3 2/2] usb: misc: xapea00x: perform platform initialization of TPM
Date: Sun, 13 May 2018 11:51:36 +0300 [thread overview]
Message-ID: <20180513085136.GC19023@linux.intel.com> (raw)
In-Reply-To: <CAAi9uDtj=nFnk2=oqhJj_c8vEenDvT5eHKaFEDGSh+u-fxg9vw@mail.gmail.com>
On Thu, May 10, 2018 at 09:31:07AM -0500, David R. Bild wrote:
> On Wed, May 9, 2018 at 8:59 PM, Jarkko Sakkinen
> <jarkko.sakkinen@linux.intel.com> wrote:
> > On Tue, May 08, 2018 at 08:36:25AM -0700, James Bottomley wrote:
> >> Early boot means userspace. for a hot pluggable device, this would
> >> probably be something in udev if you follow the no-daemon model and the
> >> daemon could do it if you do follow the daemon model.
> >>
> >
> > Could this be implemented as a first priority to daemon. If it turns out
> > to be bad approach we can reconsider kernel. If we land it to kernel it
> > is harder to take steps back.
>
> Is the daemon an implementation of the TCG resource manager spec?
>
> Best,
> David
Philip and James would be the right people to answer this. Ping? :-)
/Jarkko
next prev parent reply other threads:[~2018-05-13 8:51 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180430125418.31344-1-david.bild@xaptum.com>
2018-05-04 13:00 ` [PATCH v3 0/2] Add driver for Xaptum ENF Access card (XAP-EA-00x) David R. Bild
2018-05-04 13:00 ` [PATCH v3 1/2] usb: misc: xapea00x: add driver for Xaptum ENF Access Card David R. Bild
2018-05-07 9:58 ` Oliver Neukum
2018-05-07 13:31 ` David R. Bild
2018-05-08 9:09 ` Oliver Neukum
2018-05-04 13:00 ` [PATCH v3 2/2] usb: misc: xapea00x: perform platform initialization of TPM David R. Bild
2018-05-04 19:06 ` Jason Gunthorpe
2018-05-04 19:56 ` David R. Bild
2018-05-04 20:19 ` David R. Bild
2018-05-06 15:02 ` Jason Gunthorpe
2018-05-10 1:42 ` Jarkko Sakkinen
2018-05-08 10:55 ` Jarkko Sakkinen
2018-05-08 15:25 ` James Bottomley
2018-05-08 15:29 ` David R. Bild
2018-05-08 15:36 ` James Bottomley
2018-05-10 1:59 ` Jarkko Sakkinen
2018-05-10 14:31 ` David R. Bild
2018-05-13 8:51 ` Jarkko Sakkinen [this message]
2018-05-25 20:31 ` Ken Goldman
2018-05-10 14:25 ` David R. Bild
2018-05-10 14:47 ` James Bottomley
2018-05-10 15:17 ` David R. Bild
2018-05-25 20:23 ` Ken Goldman
2018-05-10 1:44 ` Jarkko Sakkinen
2018-05-10 14:29 ` David R. Bild
2018-05-10 1:42 ` Jarkko Sakkinen
2018-05-10 14:41 ` David R. Bild
2018-05-13 8:46 ` Jarkko Sakkinen
2018-05-14 19:31 ` Jason Gunthorpe
2018-05-14 19:59 ` David R. Bild
2018-05-14 20:08 ` Jason Gunthorpe
2018-05-14 20:12 ` David R. Bild
2018-05-07 14:12 ` EXTERNAL: " Jeremy Boone
2018-05-08 10:47 ` Jarkko Sakkinen
2018-05-10 14:09 ` David R. Bild
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=20180513085136.GC19023@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=david.bild@xaptum.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=philip.b.tricca@intel.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 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).