Comment 9 for bug 284354

the original bug was bug 274832 in which we thought that ath5k was a plain drop in replacement for madwifi, the team only got aware that NM dropped madwifi support completely very recently (sorry, none of our Q1 testers seem to use WPA) so we aimed for just switching back to it until now and our worst case plan here was to have a /etc/modprobe.d/blacklist-ath file in our -settings packages.

testing the ath5k driver from the current lbm package seems to work well now, but for obvious reasons we dont want to seed that package by default in the mobile seeds.

what still makes me curious is the fact that its apparently possible to load two concurrent modules at the same time for one hardware which seems to additionally point to a flaw in the module loading mechanism of the kernel (and produces massive races with the pm-utils scripts that unload/load the drivers on suspend/resume in no particular order).

what makes me upset is that we obviously jump on a fedora "freedom over everything, ignore the user" attitude with the whole thing here, i.e. i dont see us shipping the nuveau driver by default for nvidia cards and the ath5k situation in 2.6.27 was known beforehand apparently. what did justify the complete dropping of madwifi support ?