linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: Tim Gardner <tim.gardner@canonical.com>,
	John Linville <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: Open source driver with binary HAL for BCM4313 from Broadcom
Date: Wed, 11 Jun 2008 15:47:46 -0400	[thread overview]
Message-ID: <1213213666.19106.12.camel@dv> (raw)
In-Reply-To: <200806112047.00854.mb@bu3sch.de>

On Wed, 2008-06-11 at 20:47 +0200, Michael Buesch wrote:
> On Wednesday 11 June 2008 19:44:52 Tim Gardner wrote:
> > John,
> > 
> > Here is the URL to Broadcom's web site advertising their open source
> > driver with support for the BCM4313.
> > 
> > http://www.broadcom.com/support/802.11/linux_sta.php
> > 
> > rtg
> 
> <quote>
> Make sure that you download the appropriate tar because the hybrid binary
> file must be of the appropriate architecture type. The hybrid binary file
> is agnostic to the specific version of the Linux kernel because it is
> designed to perform all interactions with the operating system through
> operating-system-specific files...
> </quote>

Sure, they are trying to do the MadWifi thing, but it's too late since a
good free driver exists already, even if it doesn't support that
particular chip.

Still, the glue code and the headers are under GPL.  It may be useful
for reverse engineering efforts.

Perhaps the non-free object files could be used to extract firmware from
them.  But the license won't allow distribution of that firmware, if I
understand correctly.

What Broadcom could easily do is to release the firmware under a license
that would allow free distribution.  This way, the firmware would be on
installation CDs of the popular distributions, and there would be no
need to install b43-fwcutter, get the firmware (that's a challenge in
absence of a wired network), extract the firmware and install it into
the right directory.  That would make Broadcom cards make out-of-box,
and ultimately make them more popular.

Instead, Broadcom tries to control the code its users are running.  I
don't think it's going to work well.  But to be fair to them, at least
they don't pretend that Linux doesn't exit.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2008-06-11 19:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11 17:44 Open source driver with binary HAL for BCM4313 from Broadcom Tim Gardner
2008-06-11 18:47 ` Michael Buesch
2008-06-11 19:47   ` Pavel Roskin [this message]
2008-06-11 20:26     ` Stefanik Gábor
2008-06-11 21:00       ` Larry Finger
2008-06-11 21:02       ` Pavel Roskin
2008-06-11 21:31       ` Broadcom's Hybrid Driver Larry Finger
2008-06-11 21:46         ` Stefanik Gábor
2008-06-11 21:53         ` Pavel Roskin
2008-06-11 21:55           ` Johannes Berg
2008-06-11 19:50   ` Open source driver with binary HAL for BCM4313 from Broadcom Stefanik Gábor
2008-06-11 20:02     ` Larry Finger
2008-06-11 19:46 ` Stephen Hemminger
2008-06-11 21:28   ` Johannes Berg
2008-06-11 21:12 ` Hauke Mehrtens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1213213666.19106.12.camel@dv \
    --to=proski@gnu.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --cc=tim.gardner@canonical.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).