Re: [RFC 9/9] crypto: Add Samsung crypto engine driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: Maurus Cuelenaere <mcuelenaere@xxxxxxxxx>
Date: Thu, 12 Aug 2010 13:47:24 +0200

> The main issues still remain (DMA not working at all and FIFO not
> working for some (T)DES transfers). Additionally, I couldn't get
> tcrypt to test the s3c-sss driver for some reason, it always picked
> the standard AES/TDES/DES driver (even though s3c-sss has a higher
> priority and succeeded the self-test).

I forget the details of your driver, but were your encryption algorithms
implemented async?

tcrypt can validate async crypto algorithms, but cannot performance
test them just yet.  I can performance test async hash algorithms,
for which I added the code for a few months ago.
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux