2012/9/11 Yeoh Chun-Yeow <yeohchunyeow@xxxxxxxxx>: > Hi, Nick > >> Nope, with nohwcrypt we don't initialize the hw engine at all, we just >> tell hw that data is not encrypted and that nothing should be done >> about it. With these hw options from what I understand from docs we >> can initialize the engine but use only part of it, eg. use only hw >> encryption or only hw decryption. It might be useful in your case. > > The problem of ath5k right seems to be that: ' > If CCMP HW encryption is enabled, HW encryption for unicast data frame > and SW encryption for unicast management frame are possible for TX. > But for RX, both the unicast data frame and unicast management frame > are decrypted by the HW instead of doing only SW decryption for > unicast management frame. > > With the help of PCU DIAG register, possible to separate this? > Its possible to tell hw to disable decryption so that you can handle that only on sw, I haven't tested it but that's what docs say. -- GPG ID: 0xEE878588 As you read this post global entropy rises. Have Fun ;-) Nick -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
