[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161020202421.GA13459@obsidianresearch.com>
Date: Thu, 20 Oct 2016 14:24:21 -0600
From: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
Cc: "Winkler, Tomas" <tomas.winkler@...el.com>,
"tpmdd-devel@...ts.sourceforge.net"
<tpmdd-devel@...ts.sourceforge.net>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [tpmdd-devel] [PATCH] tpm, tpm_crb: remove redundant
CRB_FL_CRB_START flag
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
Powered by blists - more mailing lists