Broadcom's wireless drivers, one year later

Posted Sep 10, 2011 9:46 UTC (Sat) by slashdot (guest, #22014)
In reply to: Broadcom's wireless drivers, one year later by mjg59
Parent article: Broadcom's wireless drivers, one year later

There's always to option to leave things as they are now.

bcsmsmac stays in staging forever, and gets worked on by Broadcom engineers.

End-users mostly use b43 instead, and the b43 developers port any new feature appearing in bcsmsmac to b43 (with acknowledgements, preferably).

Broadcom's wireless drivers, one year later

Posted Sep 11, 2011 0:36 UTC (Sun) by butlerm (subscriber, #13312) [Link]

I agree. I don't see why Broadcom doesn't develop an open reference driver on an out of tree basis, according to whatever conventions they prefer, and let developers of compatible drivers use it as a reference.

That way they maintain 100% control, one code base that they can deploy across multiple operating systems, and others can do whatever they feel is appropriate for local standards, code sharing, and long term maintenance.