> I know we can't remove wext because of legacy applications but is > there anything more we can do to make the users aware that wext is > depreciated and really should be avoided? For example a onetime > kernel warning? Or is that too spammy? Anything else? The problem is that wext is in this weird hybrid state where it's really deprecated if you can use nl80211, but you are required to use wext if you can't use nl80211. Now, we disabled wext-for-cfg80211 by default, but it's still there and could be used for some cases. We probably should try to fix things, but I realize that code that never gets tested [1]. Maybe we could print a message in the special cfg80211-wext case, which has a special case in wext-core to avoid creating all those iw_handler tables? johannes [1] and yeah - people move to nl80211 once told, so there's evidently very little incentive to keep using wext, so in reality people don't really seem to have applications that only use wext even with pure cfg80211 drivers ... -- 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
