From: Jason <linux_crypto@lakedaemon.net>
To: Sebastian Andrzej Siewior <arm-kernel@ml.breakpoint.cc>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [WIP] crypto: add support for Orion5X crypto engine
Date: Tue, 03 Mar 2009 12:49:37 -0500 [thread overview]
Message-ID: <49AD6DB1.4020805@lakedaemon.net> (raw)
In-Reply-To: <20090302221058.GA11493@Chamillionaire.breakpoint.cc>
Sebastian Andrzej Siewior wrote:
> From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
>
> This is my current status of an async crypto driver for the Orion5X crypto
> unit. The driver uses the crypto accelerator.
Is this the same security engine found in the new SheevaPlug Devkit [1]? It's has the Marvell 88F6281 (Kirkwood) processor in it. This diagram [2] shows a "Security Engine", but doesn't give any detail...
I found the nuts and bolts starting at page 174 of [3], with registers listed starting on page 634.
thx,
Jason.
[1] - http://www.marvell.com/products/embedded_processors/developer/kirkwood/sheevaplug.jsp
[2] - http://www.marvell.com/products/embedded_processors/kirkwood/index.jsp
[3] - http://www.marvell.com/files/products/embedded_processors/kirkwood/FS_88F6180_9x_6281_OpenSource.pdf
next prev parent reply other threads:[~2009-03-03 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 22:10 [WIP] crypto: add support for Orion5X crypto engine Sebastian Andrzej Siewior
2009-03-03 17:49 ` Jason [this message]
2009-03-03 22:08 ` Sebastian Andrzej Siewior
2009-03-04 16:05 ` Ronen Shitrit
2009-03-04 16:35 ` Sebastian Andrzej Siewior
-- strict thread matches above, loose matches on Subject: below --
2009-05-07 21:03 Sebastian Andrzej Siewior
2009-05-07 21:39 ` Ben Dooks
2009-06-11 11:40 ` Sebastian Andrzej Siewior
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=49AD6DB1.4020805@lakedaemon.net \
--to=linux_crypto@lakedaemon.net \
--cc=arm-kernel@ml.breakpoint.cc \
--cc=linux-crypto@vger.kernel.org \
/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