On 01/22/2014 03:10 PM, Johannes Berg wrote: > On Wed, 2014-01-22 at 14:54 -0800, greearb@xxxxxxxxxxxxxxx wrote: > >> + * @IEEE80211_KEY_FLAG_SW_RX_CRYPT: This flag indicates hardware will not >> + * do any decrypt for received packets, though it may have uploaded >> + * the hardware key to be used for encrypting transmitted frames. > > This isn't needed, all you need to do is return 0 from the set_key > callback in the driver, without programming the key into the device. And > then ignore tkip key updates for such a key. I want and need to program the key into the device so that it can do the encryption for transmit. But, I need software to do full decryption on receive. That is the only way I could get ath10k to do any sort of software crypt, and in fact, that is the most efficient way to get the features I need so I might try getting ath9k to support the same mode some day... I'll be posting ath10k patches to use this soon, but the dark magic is down in the firmware in this case. Thanks, Ben > > johannes > -- Ben Greear <greearb@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.com -- 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
