Re: [PATCH 0/2] crypto: omap-sha1-md5: OMAP3 SHA1 MD5 driver

2010-04-08 Thread Herbert Xu
On Tue, Mar 23, 2010 at 07:32:39PM +0800, Herbert Xu wrote: My only question is what's your plan with respect to HMAC? If you're going to do it in hardware then it's fine as it is. Otherwise you need to implement export/import and we also need to add ahash support to hmac.c. Dmitry, did

Re: [PATCH 0/2] crypto: omap-sha1-md5: OMAP3 SHA1 MD5 driver

2010-03-24 Thread Dmitry Kasatkin
On 23/03/10 13:32, ext Herbert Xu wrote: On Wed, Mar 17, 2010 at 03:12:49PM +0200, Dmitry Kasatkin wrote: Earlier kernel contained omap sha1 and md5 driver, which was not maintained, was not ported to new crypto APIs and removed from the source tree. This driver implements async and sync

Re: [PATCH 0/2] crypto: omap-sha1-md5: OMAP3 SHA1 MD5 driver

2010-03-23 Thread Herbert Xu
On Wed, Mar 17, 2010 at 03:12:49PM +0200, Dmitry Kasatkin wrote: Earlier kernel contained omap sha1 and md5 driver, which was not maintained, was not ported to new crypto APIs and removed from the source tree. This driver implements async and sync crypto API. It still contains pr_debug()

[PATCH 0/2] crypto: omap-sha1-md5: OMAP3 SHA1 MD5 driver

2010-03-17 Thread Dmitry Kasatkin
Earlier kernel contained omap sha1 and md5 driver, which was not maintained, was not ported to new crypto APIs and removed from the source tree. This driver implements async and sync crypto API. It still contains pr_debug() for debugging purpose. Will be remove for integration. Dmitry Kasatkin