Changes with respect to v1 as per comments receivedwait, why can't the interoperability bug be fixed in the first place?
o. Rebased to linux-next as of 20091216
o. The selection is based exclusive of fsldma
o. Intoduced a new Kernel Configuration variable
*. This enables selecting the Cryptographic functionality
of Talitos along with fsldma.
*. Disables the XOR parity calculation offload, if fsldma enabled
either as kernel in-built or as a module
*. Once the inter-operability with fsldma is resolved, this option
can be removed
I agree w/Kim. We need to better understand what the bug is and how to reproduce it so we can get to the root cause.
Paper taping over it by disabling fsldma is not the right solution.