From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "Michael Frey" <mfrey@pepper.com>
Cc: "Herbert Xu" <herbert@gondor.apana.org.au>,
"Andrew Morton" <akpm@osdl.org>,
"Evgeniy Polyakov" <johnpol@2ka.mipt.ru>,
linux-crypto@vger.kernel.org, info-linux@ldcmail.amd.com
Subject: Re: crypto: Add support for the Geode AES engine (v4)
Date: Fri, 13 Oct 2006 11:34:26 -0600 [thread overview]
Message-ID: <20061013173426.GB5583@cosmic.amd.com> (raw)
In-Reply-To: <9CF4A66D-5A4B-455D-BA9C-CC62377AB4C4@pepper.com>
On 13/10/06 13:18 -0400, Michael Frey wrote:
> Does this patch support the eeprom on the AES module?
No - not yet. I wasn't happy with way we did that driver in the first
place (heaven help me, I make stupid programming decisions sometimes),
and I also wanted to get the crypto engine itself in first.
The eeprom will be coming soon - but probably not to this crowd, since
it will (for now) just be a generic device providing a bit of storage
on chip. If there is a generic way for dealing with hardware keys in
the crypto subsystem, then we can tie it together later.
> Also, Can this patch be used on a 2.6.18 kernel?
Hmmm... I use the new API - is that legal for 2.6.18?
Jordan
--
Jordan Crouse
Senior Linux Engineer
Advanced Micro Devices, Inc.
<www.amd.com/embeddedprocessors>
next prev parent reply other threads:[~2006-10-13 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <LYRIS-7332-87686-2006.10.04-02.52.47--mfrey#pepper.com@whitestar.amd.com>
2006-10-13 17:18 ` crypto: Add support for the Geode AES engine (v4) Michael Frey
2006-10-13 17:34 ` Jordan Crouse [this message]
2006-10-14 0:01 ` Herbert Xu
2006-09-27 19:31 [RFC] crypto: Add support for the Geode AES engine Jordan Crouse
2006-09-28 10:23 ` Evgeniy Polyakov
2006-09-28 21:47 ` crypto: Add support for the Geode AES engine (v2) Jordan Crouse
[not found] ` <LYRIS-4270-86789-2006.09.28-16.10.32--jordan.crouse#amd.com@whitestar.amd.com>
2006-09-28 23:17 ` crypto: Add support for the Geode AES engine (v4) Jordan Crouse
2006-09-28 23:54 ` Andrew Morton
2006-09-29 0:16 ` Jordan Crouse
2006-10-04 8:52 ` Herbert Xu
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=20061013173426.GB5583@cosmic.amd.com \
--to=jordan.crouse@amd.com \
--cc=akpm@osdl.org \
--cc=herbert@gondor.apana.org.au \
--cc=info-linux@ldcmail.amd.com \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-crypto@vger.kernel.org \
--cc=mfrey@pepper.com \
/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