From: Ken Goldman <kgoldman-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: TPM2 Driver Support in distros (part 1)
Date: Mon, 25 Jul 2016 15:23:22 -0400 [thread overview]
Message-ID: <nn5ova$1j3$1@ger.gmane.org> (raw)
In-Reply-To: <40c30de1f491455c93a79dd6f5420fc4-FoTRpVxct+aJSz+rYg/bSJowlv4uC7bZ@public.gmane.org>
On 7/25/2016 12:47 PM, Peter.Huewe-
> Speaking of PCClient based platforms, everything with:
> - Kernel >4.0 works with CRB out of the box, with FIFO if tpm_tis.force=1 as module parameter
> - Kernel >4.4 works with FIFO out of the box
1 - How does a user know whether the TPM will use CRB or FIFO - whether
to specify tpm_tis.force=1 or not?
Or can that be specified any time, and it becomes a noop for CRB?
2 - module parameter? Does that mean whatever distro dependent file is
used for the boot parameters - grub.conf or some EFI file like grub.cfg.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
next prev parent reply other threads:[~2016-07-25 19:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-24 2:53 TPM2 Driver Support in distros (part 1) Ken Goldman
2016-07-25 16:47 ` Peter.Huewe-d0qZbvYSIPpWk0Htik3J/w
[not found] ` <40c30de1f491455c93a79dd6f5420fc4-FoTRpVxct+aJSz+rYg/bSJowlv4uC7bZ@public.gmane.org>
2016-07-25 19:23 ` Ken Goldman [this message]
2016-07-25 19:40 ` Peter.Huewe-d0qZbvYSIPpWk0Htik3J/w
2016-07-25 19:46 ` Jason Gunthorpe
2016-08-11 5:35 ` Peter Huewe
2016-08-11 18:13 ` Jerry Snitselaar
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='nn5ova$1j3$1@ger.gmane.org' \
--to=kgoldman-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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).