Re: [Ocf-linux-users] Talitos not being used

[Kim P. <kim...@fr...>]

On Wed, 9 Sep 2009 18:47:11 -0700
job...@ao... wrote:

> > I am running Linux 2.6.26 on an MPC8248.  I patched my kernel with  

the 8248 has a v.1.x SEC h/w, whereas the talitos driver currently is
compatible with SEC versions 2.0+.

> > the ocf-linux-26-20080917 patch and my openssl-0.9.8e with the  
> > corresponding patch.  When I ran cryptotest, I got results for  
> > various algorithms and thought I was using the Freescale SEC.  In  
> > crypto/ocf/talitos/talitos.c, I put in some printk's and set  
> > talitos_debug to 1 to verify that the Freescale SEC was being used  
> > to do the encryption.
> >
> > Nothing was printed.  So, apparently it is not being used.  Is this  
> > a configuration issue?  My .config file follows.  Do I have  
> > something incorrectly configured for the Freescale SEC to be utilized?

even if you convince your configuration to enable the driver
(for example one would presumably provide a device tree node for
ARCH=powerpc that would fake SEC2.0 compatibility), the talitos driver
would need to be extended to support:

o the SEC1.x ring buffer (it doesn't use fetch FIFOs like the SEC2.0+)

o I don't believe the SEC1.x can do the cipher+hash, e.g. for IPsec,
in one pass.  I.e., there is no ipsec_esp descriptor.  One would have to
split the fn into two descriptor submissions to satisfy this type of
request.

o the registers and bit positions within the registers may vary for
SEC1.x->SEC2.x, depending on the part.

hth,

Kim

p.s. the upsteam kernel driver, drivers/crypto/talitos.c is in the same
boat wrt SEC1.x support - sorry.