Hi Michal:
These patches should allow you to access sha1/sha256 even when you
have your padlock modules loaded.
You can get to them as sha1-generic/sha256-generic respectively.
Let me know if you have any problems.
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>H
Hi:
As the Crypto API now allows multiple implementations to be registered
for the same algorithm, we no longer have to play tricks with Kconfig
to select the right AES implementation.
This patch sets the driver name and priority for all the AES
implementations and removes the Kconfig conditions
Hi:
This is a rewrite of the multi-algorithm patch that I posted earlier.
It now uses a flat namespace instead of the type + driver name scheme
used before.
This is the first step on the road towards asynchronous support in
the Crypto API. It adds support for having multiple crypto_alg objects
Thank you very much for your information.
I'm looking forward to seeing your results.
Cheers,
Keisuke Mera
Herbert Xu wrote:
On Wed, Nov 02, 2005 at 01:35:05PM +0900, MERA Keisuke wrote:
Could you give some informations about these, or can I have some
materials or pointers (for example, a ur
