Why Broadcom's Release May be More Significant than Just Code
On September 9 the news of Broadcom's release of the code for some of its wireless Ethernet chip sets sent shockwaves throughout the Linux community. Broadcom owners, as well as distribution developers have a reason to celebrate.
In the past, Broadcom owners had to resort to NDISwrapper or rely upon the limited reversed engineered drivers. Neither was optimal. The release of the code by Broadcom should eventually mean a much better Wi-Fi experience for owners of systems with Broadcom chip sets. But for those that like to read between the lines there may also be a deeper significance to this move.
There are two trains of thought as to the "deeper" significance in this surprising move. Some say Linux installs / computers still make up only 1% of total computers in use. Others believe it's much higher. One well-respected writer believes it is probably about 10% while another estimates it is closer to 14%. So some see the Broadcom move as proof that the higher figures are the accurate figures. The thinking being that Broadcom wouldn't worry about a mere 1% share of the market but would be concerned about a double digit market share.
The second theory, while similar in nature, is that the move is due to the growing number of large industrial and commercial Wi-Fi hot-spot networks. Many of these are relying on Linux due to its security and reliability. Again the thinking is that this is a large enough market that Broadcom does not want to lose it to a competitor that has better native Linux support, such as Intel.
Whether it's due to pressure from users, loss of sales, or just a change in attitude, it's good news for Linux and that's all that matters. Most Linux users probably don't care why, they're just happy it happened - even if it does still leave many with older chips that still may need to rely upon b43 or NDISwrapper.
Susan Linton is a Linux writer and the owner of tuxmachines.org.
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
|Introduction to MapReduce with Hadoop on Linux||Jun 05, 2013|
- Containers—Not Virtual Machines—Are the Future Cloud
- Non-Linux FOSS: libnotify, OS X Style
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Linux Systems Administrator
- Introduction to MapReduce with Hadoop on Linux
- RSS Feeds
- New Products
- Weechat, Irssi's Little Brother
- Validate an E-Mail Address with PHP, the Right Way
- Tech Tip: Really Simple HTTP Server with Python
- Poul-Henning Kamp: welcome to
13 min 18 sec ago
- This has already been done
14 min 18 sec ago
- Reply to comment | Linux Journal
59 min 32 sec ago
- Welcome to 1998
1 hour 48 min ago
- notifier shortcomings
2 hours 11 min ago
3 hours 48 min ago
- Android User
3 hours 50 min ago
- Reply to comment | Linux Journal
5 hours 43 min ago
8 hours 32 min ago
- This is a good post. This
13 hours 45 min ago
Free Webinar: Hadoop
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?