Comment 26 for bug 1097519

OK. Perhaps it would be interesting to actually define what this (1097519) bug is about. According to the first message, it's about using the brcmsmac driver for the BCM4313 chip. No more, no less.

Now lots of other, unrelated, bugs (mostly bugs about the bcmwl driver) have been merged into this one. This, to me, doesn't make sense.

If one were to "fix" this bug now it would mean that brcmsmac driver is chosen by default for BCM4313, but none of the allegedly-duplicate bcmwl bugs would be solved. Meaning people having problems with bcmwl would not have those problems solved.

Note that you may be happy with brcmsmac (which kernel version?). Please note that not everyone is using kernel 3.9 or 3.10. The linux drivers are in constant development, so what works for you now may not work with previous or future kernels. So again, you need to specify exactly which kernel applies to THIS bug.

This is the reason for saying you've made a mess of bcmwl (and hence of Ubuntu, for all I care): you have over-simplified the situation so much that now most bugs related to bcmwl are marked as incomplete or invalid, because YOUR solution is to use another driver.

Please open a bug saying "Ubuntu should default to brcmsmac for this-and-that chip using this-and-that kernel".

*I* want to use bcmwl, and *I* want bcmwl bugs being properly reported and solved (if at all possible, the core of the driver is proprietary). I might try brcmsmac with a recent kernel and see if the situation has improved. But, at least up to 3.5, brcmsmac gave me no power savings and broken channel/SSID detection, meaning not even my WLAN was found. And if found, the connection would break every minute or so.