On Sat, 2008-05-31 at 18:54 +0200, Stefanik Gábor wrote: > On Sat, May 31, 2008 at 6:48 PM, Pavel Roskin <proski@xxxxxxx> wrote: > > It's strange that other drivers (b43legacy, ath5k) use > > info->control.hw_key->hw_key_idx under the same conditions (see how > > use_encryption is calculated), but don't have any problems on the same > > network (but I need to recheck). > > Hmm... does ath5k use hardware crypto? No, it doesn't, at least with WEP, if I understand ath5k_set_key() correctly. > B43 does (but not with > nohwcrypt - and that appears to be a valid workaround), b43legacy > doesn't AFAIK. Although the code with use_encryption is present in b43legacy, it don't see any references to "set_key", so I guess you are right. Well, that explains something. -- Regards, Pavel Roskin -- 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
