From: Dan Williams <dcbw@redhat.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Henry Ptasinski <henryp@broadcom.com>,
Brett Rudley <brudley@broadcom.com>,
Nohee Ko <noheek@broadcom.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
b43-dev <b43-dev@lists.infradead.org>
Subject: Re: Request for free-distributable Broadcom's (G|LP)-PHY firmware
Date: Thu, 21 Oct 2010 10:21:57 -0500 [thread overview]
Message-ID: <1287674517.2383.7.camel@dcbw.foobar.com> (raw)
In-Reply-To: <AANLkTinfwhjvfJU6C97SPJ8YKRqyJaCoQnAcC_uKLZa=@mail.gmail.com>
On Thu, 2010-10-21 at 00:11 +0200, Rafał Miłecki wrote:
> W dniu 20 października 2010 23:50 użytkownik Henry Ptasinski
> <henryp@broadcom.com> napisał:
> > Sorry for the delay in responding. We are exploring what is possible but
> > for the moment the answer is no. At present our focus is on providing the
> > best open source solution we can for 4313, 43224, 43225, 4329 and future
> > chips sets.
>
> Thanks for answer.
>
> Please, can you make totally sure person responsible for this gets it
> totally right? I believe it's very important.
>
> The easiest step for you, which we still would appreciate is really
> trivial one. It's *not* about writing any code, *not* about releasing
> anything new. It's just about releasing in under friendly license.
> This firmware is already available, we have access to it, we use it.
> The problem is that distributions can not ship it.
>
> If you let me use simplification: all we need as first nice step is
> Broadcom to say: "You can use it".
That's not enough to allow Fedora to ship it. We'd need a clear license
from Broadcom (ex the existing Intel or Marvell firmware licenses)
before Fedora could feel comfortable about shipping it legally in all
jurisdictions.
http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=blob;f=LICENCE.mwl8k;h=3224e1bbfba8ccd1d980f57eb88378f20bb2d146;hb=HEAD
http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=blob;f=LICENCE.libertas;h=1fd8766c26a170b50605455ae6f54b607baa12cf;hb=HEAD
There's an existing Broadcom license in linux-firmware.git, and it *may*
be OK, but it's really, really long and given that other major companies
adopted the "shorter is better" approach, it's hard to believe that all
the existing Broadcom license text is actually needed.
Dan
next prev parent reply other threads:[~2010-10-21 15:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 22:07 Request for free-distributable Broadcom's (G|LP)-PHY firmware Rafał Miłecki
2010-10-08 22:07 ` Rafał Miłecki
2010-10-19 0:02 ` Rafał Miłecki
2010-10-19 0:02 ` Rafał Miłecki
2010-10-19 0:30 ` Greg KH
2010-10-20 21:50 ` Henry Ptasinski
2010-10-20 22:11 ` Rafał Miłecki
2010-10-20 22:11 ` Rafał Miłecki
2010-10-20 22:13 ` Luis R. Rodriguez
2010-10-20 22:13 ` Luis R. Rodriguez
2010-10-21 15:21 ` Dan Williams [this message]
2011-02-18 21:24 ` Rafał Miłecki
2011-02-18 21:24 ` Rafał Miłecki
2011-02-18 22:21 ` Larry Finger
2011-02-18 22:21 ` Larry Finger
2011-02-21 9:59 ` Stanislaw Gruszka
2011-02-21 14:23 ` Gábor Stefanik
2011-02-21 14:23 ` Gábor Stefanik
2011-02-21 14:49 ` Rafał Miłecki
2011-02-21 14:49 ` Rafał Miłecki
2011-02-21 19:15 ` Luis R. Rodriguez
2011-02-21 19:15 ` Luis R. Rodriguez
2011-02-21 16:09 ` Larry Finger
2011-02-21 16:09 ` Larry Finger
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=1287674517.2383.7.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=b43-dev@lists.infradead.org \
--cc=brudley@broadcom.com \
--cc=gregkh@suse.de \
--cc=henryp@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=noheek@broadcom.com \
--cc=zajec5@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.