Comment 21 for bug 37773

If:
 * My current experiments with adding madwifi-ng support to wpasupplicant (without remove madwifi-old support) are succesful
 * I can somehow make network-manager discover whether it's dealing with a madwifi-ng controlled wifi card or not and pass the appropriate options to wpasupplicant
 * We can identify exactly which cards are causing this issue

...we just might be able to pursuade someone into making madwifi-ng the default for those particular cards.