Re: [Ocf-linux-users] Geode LX800 and VIA PADLOCK

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

Jivin Marco lays it down ...
> Hi,
> 
> I have to use the cpus in object. I'd like to use OCF. I see a bit the
> code and I don't understand a thing: is the framework compatible with
> the kernel driver already inserted in mainline? I mean, in the kernel
> there are the driver for those cpus but I don't see the support of OCF,
> is the framework smart to use the kernel drivers instead of rewriting a
> similar ones for ocf? I have this doubt because I see some driver like
> talitos both in OCF and in the kernel, are they different?

No,  they are the same,  OCF had a talitos driver first ;-)

If you don't want to use the OCF version of the driver,  use the kernel
version and then use the OCF "cryptosoft" driver which uses the kernel
crypto API (be it HW or SW to do the work).

> If for example I want to use the sec engine and so the talitos driver, do I
> have to enable the talitos support both in the ocf menu and in hw driver
> kernel menu? Can anyone quickly explain to me the management of the
> driver in ocf?

The talitos driver is relatively up to date in OCF,  though the kernel
version gets more attention.

You have two options:

	1. Enable the OCF talitos driver and do not enable the kernel
	   version
	
	2. Enable the kernel version,  and enable the OCF cryptosoft
	   driver.

Depending on your application you may better served by one of the
options.  Using the talitos driver through cryptosoft+OCF would not be
ideal IMO,

Cheers,
Davidm

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