On 26 October 2010 09:52, Nikos Mavrogiannopoulos wrote:
> Did you apply this patch as well?
> http://repo.or.cz/w/cryptodev-linux.git/blob/HEAD:/extras/openssl-0.9.8l-cryptodev-aes256.patch
Damn, I was sure I did but I forgot to push the patch from the quilt series.
Thank you again,
Luca
___
On Mon, Oct 25, 2010 at 11:41 PM, Luca Niccoli wrote:
>> I remember I needed an extra flag to use the actual engine in speed. Did
>> you try openssl speed -evp aes-128-cbc -engine ...?
> That did it.
[...]
> which makes me think (together with the driver source) that the CESA engine
> supports 256
On October 25, 2010 - 21:13, Nikos Mavrogiannopoulos wrote:
> I remember I needed an extra flag to use the actual engine in speed. Did
> you try openssl speed -evp aes-128-cbc -engine ...?
That did it.
I really couldn't find this info anywhere...
Do you know why openssl uses the hardware engine o
On 10/25/2010 07:08 PM, Luca Niccoli wrote:
> I compiled and tested both 0.7 and git
> (ad67bbd1ae0b366455c9ca61334399930fc43ae2); I can successfully use the
> example programs and the CESA crypto engine of my openrd board is used
> (I can see it from the speedup and /proc/interrupts).
> I refreshe
I compiled and tested both 0.7 and git
(ad67bbd1ae0b366455c9ca61334399930fc43ae2); I can successfully use the
example programs and the CESA crypto engine of my openrd board is used
(I can see it from the speedup and /proc/interrupts).
I refreshed the patches included in extra/ and compiled
openssl-
