Hi, > Is there some technical reason why module ks7010 includes a > implementation of Michael MIC instead of using the implementation in > crypto/? > > Or is this covered by the statement from the TODO > > - check what other upstream wireless mechanisms can be used instead of the > custom ones here Exactly. Furthermore, for this driver to ever go upstream, it needs to be converted from WEXT to cfg80211. I didn't look super much into it, but from what I grasped, the Michael conversion comes with the above conversion "for free". Regards, Wolfram
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
