From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Joel Schopp <jschopp@linux.vnet.ibm.com>,
tpmdd-devel@lists.sourceforge.net, linuxppc-dev@lists.ozlabs.org
Subject: Re: [tpmdd-devel] Has anyone a ATMEL TPM Chip on PPC64 (CONFIG_TCG_ATMEL)?
Date: Tue, 29 Oct 2013 01:03:26 +0100 [thread overview]
Message-ID: <201310290103.26678.PeterHuewe@gmx.de> (raw)
In-Reply-To: <20131028234745.GB26666@obsidianresearch.com>
Am Dienstag, 29. Oktober 2013, 00:47:45 schrieb Jason Gunthorpe:
> On Mon, Oct 28, 2013 at 01:03:43PM -0500, Joel Schopp wrote:
> > 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
>
> Hurm, that is crazy, because tpm_atmel.h contains an #else block for
> !CONFIG_PPC64. The single major source of complexity in this driver is
> that else block.
>
Argh, sorry my bad.
Of course it's available on other archs as well, since it's
PPC64 _||_ HAS_IOPORT
d'oh - sorry.
Peter
prev parent reply other threads:[~2013-10-29 0:00 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 ` [tpmdd-devel] " Joel Schopp
2013-10-28 23:47 ` Jason Gunthorpe
2013-10-29 0:03 ` Peter Hüwe [this message]
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=201310290103.26678.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=jgunthorpe@obsidianresearch.com \
--cc=jschopp@linux.vnet.ibm.com \
--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).