* Ben Dooks | 2009-05-07 22:39:22 [+0100]:
Sorry for the late reply.
diff --git a/drivers/crypto/mv_crypto.c b/drivers/crypto/mv_crypto.c
new file mode 100644
index 000..40eb083
--- /dev/null
+++ b/drivers/crypto/mv_crypto.c
+struct req_progress {
+struct sg_mapping_iter
The only functional part is ecb-aes in encryption mode. The decryption
seems to work in 16 byte key mode. According to the spec [1] the
decryption key is different and has to be computed by the HW.
Chapter 11.1.4 says, that the decryption key is computed by performing a
dummy encrypt operation.
* Ronen Shitrit | 2009-03-04 18:05:12 [+0200]:
However a SW calculation is also possible.
Chapter 11.1.4 in [1] says, that the decrypt key is the last 16/24/32 bytes
created by the expansion algorithm. So I picked the key expand routine
from generic aes module and just passed the crypto test for
Sebastian Andrzej Siewior wrote:
From: Sebastian Andrzej Siewior sebast...@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
* Jason | 2009-03-03 12:49:37 [-0500]:
I found the nuts and bolts starting at page 174 of [3], with registers
listed starting on page 634.
they look the same to me. The registers seem to be on the same spot, the
description is the same from what I recall.
thx,
Jason.
Sebastian
--
To
