From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: linuxppc-dev@lists.ozlabs.org, tpmdd-devel@lists.sourceforge.net
Subject: Has anyone a ATMEL TPM Chip on PPC64 (CONFIG_TCG_ATMEL)?
Date: Sun, 27 Oct 2013 23:06:09 +0100 [thread overview]
Message-ID: <201310272306.09310.PeterHuewe@gmx.de> (raw)
Hi,
I was wondering if anyone here on this list still has a machine with an old=
=20
ATMEL TPM (trusted platform module) lying around?
=46rom the kconfig entry it becomes evident that it was only supported on p=
pc64=20
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=20
will be accessible from within Linux. To compile this driver=20
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=
=20
that made it unusable for the last 6 years ;)
So if anyone still has this kind of hardware around, please reply.
Thanks,
Peter
next reply other threads:[~2013-10-27 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 22:06 Peter Hüwe [this message]
2013-10-28 18:03 ` [tpmdd-devel] Has anyone a ATMEL TPM Chip on PPC64 (CONFIG_TCG_ATMEL)? Joel Schopp
2013-10-28 23:47 ` 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=201310272306.09310.PeterHuewe@gmx.de \
--to=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).