Re: [Ocf-linux-users] AES hardware accelerator in OpenSSL with OCF

[David M. <Dav...@se...>]

Jivin Palacios, Hector lays it down ...
> > -----Original Message-----
> > From: Hector Palacios [mailto:hec...@di...]
> > Sent: Friday, January 30, 2009 12:16 PM
> > To: David McCullough
> > Cc: ocf...@li...
> > Subject: Re: [Ocf-linux-users] AES hardware accelerator in OpenSSL with
> > OCF
> > 
> > I don't see many differences between the way aes_generic loads the
> > algorithm and the way my driver does it. The main difference is that
> > aes_generic cra_flags is CRYPTO_ALG_TYPE_CIPHER while my driver is
> > CRYPTO_ALG_TYPE_ABLKCIPHER | CRYPTO_ALG_ASYNC.
> > In other words, my driver uses .cra_u.ablkcipher to define the crypto
> > functions while the aes_generic uses .cra_u.cipher. Do you know if this
> > makes any difference to OCF layer?
> 
> Hello,
> 
> I have solved the problem to make OCF work with my hw acceleration driver.
> My driver is developed as an async block cipher (ablkcipher) and OCF did not have support but for blockciphers (sync).
> I have done some really "quick & dirty" hacks to include support for ablkciphers in cryptosoft.c module.
> They are really "dirty" because I don't know the internals of OCF, but they do the magic of linking my driver to OpenSSL which is what I wanted.
> I attach here the patch I did to cryptosoft.c just in case anybody finds it interesting.

Great,  thanks for that.  I'll see if I can merge that in when I get
some cycles,

Cheers,
Davidm

-- 
David McCullough,  dav...@se...,  Ph:+61 734352815
McAfee - SnapGear  http://www.snapgear.com                http://www.uCdot.org