On Wed, Nov 11, 2015 at 09:54:37AM -0500, Orlando wrote: > I think the main problem might be my lack of understanding how IVs are > handled by the kernel crypto framework. It seems the omap-aes.c driver > is indicating to the crypto framework that it wants IV generation to > be handled automatically by the crypto framework by filling this field > .geniv = "eseqiv". Is there a way I can tell the kernel crypto > framework to stop handling IV generation? Even if I remove the .geniv > field it gets set with a default value by the crypto framework. I have > tried .geniv = "<built-in>" but then when I make a crypto call it does > not use the driver anymore. What are the required things I must do if > I set .geniv = "<built-in>" ?
geniv is completely unrelated to this. In fact, in the current kernel geniv is no longer used and I will remove it once the skcipher conversion is done. Cheers, -- Email: Herbert Xu <herb...@gondor.apana.org.au> 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
