On Wed, Jul 27, 2016 at 11:05:14AM -0500, George Wilson wrote: > > Yes, generally Linux expects DT to be set correctly by the boot > > firmware. Early firmware needs to know the TPM type anyhow to do the > > TPM setup, so this doesn't seem like a realistic scenario. > > A reset is required after upgrade/downgrade. But the version still > needs to be detected by the firmware somehow. It could be configured > manually in firmware state after the upgrade/downgrade to properly set > the property, which seems much less desirable than a probe.
Well, the firmware has to take care of this. If the firmware wants to support switchable firmware it needs to be able to do probe that works with all the firmware versions. ACPI and DT both expect the TPM version to be passed to the OS, it is up to the firmware to do that correctly.. The fact you've already seen TPM2 probing failures makes me very reluctant to turn it on more broadly, and maybe even think we should get rid of it from tis too.. Jason ------------------------------------------------------------------------------ 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 _______________________________________________ tpmdd-devel mailing list tpmdd-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
