Broadcom's wireless drivers, one year later

Posted Sep 1, 2011 2:15 UTC (Thu) by paragw (guest, #45306)
In reply to: Broadcom's wireless drivers, one year later by mjg59
Parent article: Broadcom's wireless drivers, one year later

"We could keep b43 for ssb devices and leave bcma devices to brcmsmac, but that would result in some duplication of phy code."

That to me sounds like the only practical option - even attractive one given the others. If we are not talking tens of thousands of LOC - I don't see why that it would be so bad.

May be some portion of "baked" phy code can be made common and shared across b43 and brcmsmac - the one that is totally obvious and is not likely to change much.

to post comments

Broadcom's wireless drivers, one year later

Posted Sep 1, 2011 23:48 UTC (Thu) by mb (subscriber, #50428) [Link] (1 responses)

> That to me sounds like the only practical option - even attractive one given the others. If we are not talking tens of thousands of LOC - I don't see why that it would be so bad.

What about embedded BCMA? brcmsmac doesn't support it.

Broadcom's wireless drivers, one year later

Posted Sep 2, 2011 3:10 UTC (Fri) by paragw (guest, #45306) [Link]

>What about embedded BCMA? brcmsmac doesn't support it.

That's drivers/bcma right? Additional 1727 lines of code on top of b43+ssb - which isn't all that bad. May be getting rid of duplicate hardware support from b43 could compensate some.