Broadcom's wireless drivers, one year later
Broadcom's wireless drivers, one year later
Posted Sep 1, 2011 8:15 UTC (Thu) by mjthayer (guest, #39183)In reply to: Broadcom's wireless drivers, one year later by mhelsley
Parent article: Broadcom's wireless drivers, one year later
> The article remains quite correct. It really doesn't matter whether closed source processes are better or worse. The real issue is whether/how the *kernel* process can/will be improved to help avoid "wasting" those resources.
Dare I ask, might part of the problem here be lumping too much together into one piece of software? If you look into user-space, you see healthy competition between (free) projects such as NetworkManager and ConnMan [1] which presumably benefit both and all users. I'm not saying that a situation where every driver lives for itself, as is customary in other OSes (or the old situation where every wireless driver on Linux included its own IEEE 802.11 stack), would be an improvement, but if say competing complete wireless subsystems complete with drivers could co-exist without one of them having to be the single chosen one, we might be able to cut out some of the time wasted on politics. No, I didn't say the MK word.