From bjorn.helgaas@hp.com on tpm-devel mailing list:
There is no "PNPACPI" driver interface as such. PNPACPI is an
internal backend of PNP, and drivers just use the generic PNP
interface.
The drivers should depend on CONFIG_PNP, not CONFIG_PNPACPI.
tpm_nsc.c doesn't use PNP at all, so we can just remove the
dependency completely. It probably *should* use PNP to
discover the device, but until it does, there's no point
in depending on PNP.
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
--- work7.orig/drivers/char/tpm/Kconfig 2008-03-27 14:22:18.000000000 -0600
+++ work7/drivers/char/tpm/Kconfig 2008-03-27 15:42:22.000000000 -0600
@@ -23,7 +23,7 @@
config TCG_TIS
tristate "TPM Interface Specification 1.2 Interface"
- depends on PNPACPI
+ depends on PNP
---help---
If you have a TPM security chip that is compliant with the
TCG TIS 1.2 TPM specification say Yes and it will be accessible
@@ -32,7 +32,6 @@
config TCG_NSC
tristate "National Semiconductor TPM Interface"
- depends on PNPACPI
---help---
If you have a TPM security chip from National Semiconductor
say Yes and it will be accessible from within Linux. To
@@ -48,7 +47,7 @@
config TCG_INFINEON
tristate "Infineon Technologies TPM Interface"
- depends on PNPACPI
+ depends on PNP
---help---
If you have a TPM security chip from Infineon Technologies
(either SLD 9630 TT 1.1 or SLB 9635 TT 1.2) say Yes and it
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
tpmdd-devel mailing list
tpmdd-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tpmdd-devel