From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: "Winkler, Tomas" <tomas.winkler@intel.com>,
"tpmdd-devel@lists.sourceforge.net"
<tpmdd-devel@lists.sourceforge.net>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [tpmdd-devel] [PATCH] tpm, tpm_crb: remove redundant CRB_FL_CRB_START flag
Date: Thu, 20 Oct 2016 14:24:21 -0600 [thread overview]
Message-ID: <20161020202421.GA13459@obsidianresearch.com> (raw)
In-Reply-To: <20161020140011.s5mu3atjjwnwqda4@intel.com>
On Thu, Oct 20, 2016 at 05:00:11PM +0300, Jarkko Sakkinen wrote:
> > > I have a 4th Gen Core NUC where I experienced this issue. It reported
> > > requiring only ACPI start but actually required ACPI + CRB start. The
> > > comment could have been better.
Shouldn't bios work arounds be keyed on something? What happens if a
system rolls around that cannot do ACPI + CRB start? How does this
system work in windows?
Jason
next prev parent reply other threads:[~2016-10-20 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 20:42 [PATCH] tpm, tpm_crb: remove redundant CRB_FL_CRB_START flag Jarkko Sakkinen
2016-10-17 22:51 ` Jarkko Sakkinen
2016-10-19 10:28 ` [tpmdd-devel] " Winkler, Tomas
2016-10-19 16:09 ` Jarkko Sakkinen
2016-10-20 13:59 ` Jarkko Sakkinen
2016-10-20 14:00 ` Jarkko Sakkinen
2016-10-20 20:24 ` Jason Gunthorpe [this message]
2016-10-21 15:11 ` Jarkko Sakkinen
2016-10-25 20:31 ` Jarkko Sakkinen
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=20161020202421.GA13459@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox