Boycott Laptops with Broadcom WiFi

It seems to be a recurring theme, but we keep hearing about different WLAN parts that don't work with NDIS wrapper, or other problems building the NDIS wrapper etc.

I've never used the NDIS wrapper, and I refuse to do so. I also refuse to purchase or recommend any laptop with a Broadcom WLAN part on it, at least until Broadcom changes their position and makes it possible for 3rd parties (even under NDA) to develop device drivers for their WLAN products.

The reason is simple: until laptop manufacturers start losing sales due to people who take the same position, they won't stop including Broadcom WLAN on their products. The loss of a few individual WLAN cards won't impact Broadcom at all, but if Gateway or Dell stops purchasing WLAN parts, then its a whole new ballgame. And the more laptop vendors that we can get to understand that use of Broadcom leads to lost sales, the more impact it will have.

Either Broadcom will take notice, and correct their behavior (e.g. by offering 3rd parties access to device driver info under NDA, writing drivers themselves for platforms like OpenSolaris, or even better, offering up open technical specs), or their WLAN products will gradually fade from popularity so that they are no longer relevant.

To be honest, I don't care which result comes about. But please, don't use or purchase Broadcom WLAN. And to those of you writing neat things like NDIS wrapper and reverse engineering efforts like the bwi driver in *BSD, I'd recommend you rethink whether enabling further sales of laptops bundled with Broadcom WLAN is really something you want to encourage.

(For specific alternatives to Broadcom WLAN, look for either Intel or Atheros WIFI.)

Comments

+1

Do you mind if I copy this to my blog as well ?

Regards,
Edward.
Unknown said…
Of course not, feel free to quote me.
Thanks man ;)
Trying to get such a message as this out is quite hard work.
Regards,
Anonymous said…
The lack of opensource drivers is just part of the problem; their hardware is just plain awful. I've yet to see a single device where Broadcom chips are used, where the experience is anything but terrible.

Apple for instance, in the latest MacBooks changed their wireless from Atheros to Broadcom. As soon as they did it, there was the beginning of Apple users complaining about poor wireless reliability.

I on occasions hang out on Windows forums; everytime I see a post along the lines of 'wifi problems', I bet to myself it is a broadcom. 9/10, its a Broadcom.

So if it isn't boycotting it for the lack of willingness to allow third parties to create drivers, it should be at the very least because their products are crud.

Popular posts from this blog

The Hand May Be Forced

Well, as you may have read , Oracle has decided that at some point very soon, we're going to lose normal regular access to the source code for OS/Net. (I.e. the Solaris kernel and supporting programs.) While I would have vastly preferred for Illumos to have a cooperative and collaborative relationship with Oracle , it appears that Oracle doesn't value this. In fact, the exact words were from the management at Oracle were as follows: Solaris is not something we outsource to others, it is not the assembly of someone else’s technology, and it is not a sustaining-only product. While I understand the need to own the technology, there are few things that could be stated that show a stronger NIH attitude than this. Its unlikely that there will ever be a way for Oracle and the greater community to have a collaborative relationship. This is a dark day for OpenSolaris -- its effectively dead now. (Its parent, Solaris, lives on however.) How unfortunate. For Oracle that is. Because...

GNU grep - A Cautionary Tale About GPLv3

My company, DEY Storage Systems , is in the process of creating a new product around the illumos operating system.  As you might imagine, this product includes a variety of open and proprietary source code.  The product itself is not delivered as a separate executable, but as a complete product.  We don't permit our customers to crack it open, both from the sense of protecting our IP, but also to protect our support and release engineering organizations -- our software releases consist only of a single file and we don't supply tools or source for other parties to modify that file. One of the pieces that we wanted to integrate into the tree is an excellent little piece of software called Zookeeper , produced by the Apache organization.  Like illumos, Zookeeper has a nice non-viral copyleft license, which makes it nice for integration into our product. However, I discovered that as part of our integration, one of my engineers had decided to integrate GNU grep. ...

MacOS X 10.10.3 Update is *TOXIC*

As a PSA (public service announcement), I'm reporting here that updating your Yosemite system to 10.10.3 is incredibly toxic if you use WiFi. I've seen other reports of this, and I've experienced it myself.  What happened is that the update for 10.10.3 seems to have done something tragically bad to the WiFi drivers, such that it completely hammers the network to the point of making it unusable for everyone else on the network. I have late 2013 iMac 27", and after I updated, I found that other systems started badly badly misbehaving.  I blamed my ISP, and the router, because I was seeing ping times of tens of seconds ! (No, not milliseconds, seconds!!!   In one case I saw responses over 64 seconds.)  This was on other systems that were not upgraded.  Needless to say, that basically left the network unusable. (The behavior was cyclical -- I'd get a few tens of seconds where pings to 8.8.8.8 would be in the 20 msec range, and then it would start to jump up v...