From: "Rafał Miłecki" <zajec5@gmail.com>
To: Henry Ptasinski <henryp@broadcom.com>
Cc: 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: Request for free-distributable Broadcom's (G|LP)-PHY firmware
Date: Thu, 21 Oct 2010 00:11:23 +0200 [thread overview]
Message-ID: <AANLkTinfwhjvfJU6C97SPJ8YKRqyJaCoQnAcC_uKLZa=@mail.gmail.com> (raw)
In-Reply-To: <4CBF640C.4080405@broadcom.com>
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".
--
Rafa?
next prev parent reply other threads:[~2010-10-20 22:11 UTC|newest]
Thread overview: 10+ 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-19 0:02 ` Rafał Miłecki
[not found] ` <4CBF640C.4080405@broadcom.com>
2010-10-20 22:11 ` Rafał Miłecki [this message]
2010-10-20 22:13 ` Luis R. Rodriguez
[not found] ` <1287674517.2383.7.camel@dcbw.foobar.com>
2011-02-18 21:24 ` Rafał Miłecki
2011-02-18 22:21 ` Larry Finger
[not found] ` <20110221095957.GA4568@redhat.com>
2011-02-21 14:23 ` Gábor Stefanik
2011-02-21 14:49 ` Rafał Miłecki
2011-02-21 19:15 ` Luis R. Rodriguez
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='AANLkTinfwhjvfJU6C97SPJ8YKRqyJaCoQnAcC_uKLZa=@mail.gmail.com' \
--to=zajec5@gmail.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 \
/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).