On Fri, May 25, 2012 at 06:08:26PM +0200, Phil Sutter wrote: > > The point for this being RFC is backwards-compatibility: earlier > hardware (Orion) ships a (slightly) different DMA engine (IDMA) along > with the same crypto engine, so in fact mv_cesa.c is in use on these > platforms, too. But since I don't possess hardware of this kind, I am > not able to make this code IDMA-compatible. Also, due to the quite > massive reorganisation of code flow, I don't really see how to make TDMA > support optional in mv_cesa.c. So does this break existing functionality or not? Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
