[PATCH 00/20] staging: brcm80211: 7th reaction for mainline patch #2
John W. Linville
linville at tuxdriver.com
Wed Sep 21 06:40:56 PDT 2011
On Tue, Sep 20, 2011 at 10:56:49PM +0200, Rafał Miłecki wrote:
> 2011/9/20 Johannes Berg <johannes at sipsolutions.net>:
> > On Tue, 2011-09-20 at 06:03 -0700, Greg KH wrote:
> >> And while code is great and nice, I still haven't seen any real answers
> >> to all of the questions that were asked of the Broadcom driver team
> >> during that review by the linux-wireless developers about how things
> >> will be handled properly due to the overlap in functionality with the
> >> existing "real" driver in the tree.
> > Let's qualify this to "some developers".
> > One thing I'd like to point out is that the Broadcom's firmware API has
> > always undergone changes over time. I'm actually surprised that b43
> > works as well as it does (which, tbh, isn't very well at all, at least
> > for me with some 11n PHY). I also don't think that Broadcom are going to
> > maintain compatibility and/or maintain new firmware features for old
> > devices, that just doesn't make any sense.
> Actually, when we got some single response from Broadcom about their
> relation to b43, they haven't mentioned support for old HW is any
> problem at all. They just pointed we don't support calibration for
> N-PHY and we don't support 802.11n feature for a better performance.
> I feel we're creating some problems ourself. Just some guessing that
> support for older HW can be real problem for future development... not
> confirmed by anyone at all.
Their new firmware doesn't run on the older hardware, no?
John W. Linville Someday the world will need a hero, and you
linville at tuxdriver.com might be all we have. Be ready.
More information about the devel