From: Joel Schopp <jschopp@linux.vnet.ibm.com>
To: "Peter Hüwe" <PeterHuewe@gmx.de>,
linuxppc-dev@lists.ozlabs.org, tpmdd-devel@lists.sourceforge.net
Subject: Re: [tpmdd-devel] Has anyone a ATMEL TPM Chip on PPC64 (CONFIG_TCG_ATMEL)?
Date: Mon, 28 Oct 2013 13:03:43 -0500 [thread overview]
Message-ID: <526EA6FF.2080401@linux.vnet.ibm.com> (raw)
In-Reply-To: <201310272306.09310.PeterHuewe@gmx.de>
On 10/27/2013 05:06 PM, Peter Hüwe wrote:
> Hi,
>
> I was wondering if anyone here on this list still has a machine with an old
> ATMEL TPM (trusted platform module) lying around?
>
>>From the kconfig entry it becomes evident that it was only supported on ppc64
> machines.
>
> config TCG_ATMEL
> tristate "Atmel TPM Interface"
> depends on PPC64 || HAS_IOPORT
> ---help---
> If you have a TPM security chip from Atmel say Yes and it
> will be accessible from within Linux. To compile this driver
> as a module, choose M here; the module will be called tpm_atmel.
>
> The hardware/driver is pretty old and the driver might have contained a bug
> that made it unusable for the last 6 years ;)
>
> So if anyone still has this kind of hardware around, please reply.
>
As near as I can tell this was on a single machine type (the js21 circa
2006). The firmware on the machine didn't support establishing a root
of trust, so use of the TPM was as a practical matter effective only for
the other functions like random number generation and key management.
The number of users who used the TPM for this on this machine was likely
very small 7 years ago. The number of those machines still in service
today is likely smaller still. The cross section of those two small
numbers combined with those who want to run on a shiny new kernel has to
be quickly approaching zero.
I reccomend removing the driver. If the stars align and a user actually
appears who wants to use one I'll clean up the driver and resubmit it
for inclusion. I just don't think that will happen.
-Joel
next prev parent reply other threads:[~2013-10-28 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 22:06 Has anyone a ATMEL TPM Chip on PPC64 (CONFIG_TCG_ATMEL)? Peter Hüwe
2013-10-28 18:03 ` Joel Schopp [this message]
2013-10-28 23:47 ` [tpmdd-devel] " Jason Gunthorpe
2013-10-29 0:03 ` Peter Hüwe
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=526EA6FF.2080401@linux.vnet.ibm.com \
--to=jschopp@linux.vnet.ibm.com \
--cc=PeterHuewe@gmx.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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).