archive mirror
 help / color / mirror / Atom feed
* /dev/tmprm0 resource manager not created for tpm_crb KLM
@ 2017-04-20 19:04 Nasim, Kam
  0 siblings, 0 replies; only message in thread
From: Nasim, Kam @ 2017-04-20 19:04 UTC (permalink / raw)
  To: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f

[-- Attachment #1.1: Type: text/plain, Size: 995 bytes --]


For TPM 2.0, we would like to use the in-kernel RM, in order to have multiple apps connecting concurrently to my TPM device.

Since I am on CentOS 7.3, which is still on Kernel v3.10 (with 4.00 backports), I had to build the TPM Kernel driver out of tree and load it in a 3.10 Kernel.

However I am not seeing any /dev/tpmrm0 character device being created after the tpm_crb KLM gets loaded.

Is there any additional configuration required to make this device node that I may not have backported to v3.10? I only picked from the <kernel>/drivers/char/tpm subtree.

Also how do I access the TPM2 event logs? Would the tpmrm0 device node only be created on boot?  (I see that if I delete the /dev/tpm0 device and reload the kernel module, the device does NOT get created)

Any help you folks can offer me would be greatly appreciated.


Kam Nasim, Software Engineer - Titanium Cloud, Wind River
direct 613.963.9926  mobile 613.408.3688  skype kamnasim

[-- Attachment #1.2: Type: text/html, Size: 4158 bytes --]

[-- Attachment #2: Type: text/plain, Size: 202 bytes --]

Check out the vibrant tech community on one of the world's most
engaging tech sites,!

[-- Attachment #3: Type: text/plain, Size: 192 bytes --]

tpmdd-devel mailing list

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2017-04-20 19:04 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-04-20 19:04 /dev/tmprm0 resource manager not created for tpm_crb KLM Nasim, Kam

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).