W dniu 26 sierpnia 2011 19:55 użytkownik Henry Ptasinski <henryp@xxxxxxxxxxxx> napisał: > On Thu, Aug 25, 2011 at 01:55:26PM -0700, Rafał Miłecki wrote: >> 2011/8/25 Henry Ptasinski <henryp@xxxxxxxxxxxx>: >> > With the latest series of cleanup patches merged in by Greg KH, I'd like to >> > once again propose moving brcm80211 out of staging and into mainline. >> >> Henry: a simple question, please explain it to me, what brcmsmac does >> provide that b43 doesn't? > > The brcmsmac driver supports the BCM4313, BCM43224, and BCM43225 chipsets with > full performance i.e. rate vs. range comparable to what's achived with these > chips running under other operating systems. > > The underlying phy algorithms, especially the dynamic calibrations, have been > designed and tested, over the full range of chip operating temperatures, and > across fabrication process corners, to maximize the performance acheived in all > cases. Are you aware, that b43's code comes from RE efforts and PHY part is mostly identical to brcmsmac/wl's one? We have the same functions, conditions, operations here. Sometimes called in a different way, sometimes we have different code structures, but generally code is the same. So I still don't see the advantages of using brcmsmac instead of b43. > The driver is fully supported by Broadcom, and provides an API for addition of > phy support for newer chipsets that will help speed up the process of getting > support for those chipsets into the kernel. I'm glad you're so proud of yours flexible API, but b43 has the same implemented since 2008. You can see we've just easily added support for HT-PHY using our API and I'm working on LCN-PHY right now (without modifying the API). We would like to have b43 supported by Broadcom. It sounds much better, I've shown you a lot of advantages of such a choice. Switching to brcmsmac on the other hand needs a lot of work and improvements. -- Rafał -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
