> You guys obviously don't want to support legacy hardware. So there is > absolutely > no way to drop b43 in favor of brcmsmac. That is _impossible_. > And I do agree that it would be completely insane for you guys to support > the legacy > b43 802.11g code. > > The other way around, dropping brcmsmac in favor of b43 would be insanely > stupid, too. > It would basically be dropping broadcom-linux-wlan support. Nobody wants > that. Agree and we are not proposing that. We did however initially propose (and implement) a dividing line of ssb chips for b43 and AXI based chips for brcmsmac but b43 team chose to ignore/reject that. I haven't heard any counter-proposal from b43. We would love to hear one. > I do, however, think that a separate broadcom-supported PHY module should > be created, > that is used by both brcmsmac and b43. I'm not totally opposed to that idea but it does not solve the primary issue of conflicting b43 and brcmsmac modules. Brett _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
