From: "Arend van Spriel" <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: lina <lina.lastname@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Debian Lists" <debian-user@lists.debian.org>,
Camaleón <noelamac@gmail.com>,
"b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>
Subject: Re: bcm4331 firmware installer package
Date: Thu, 22 Dec 2011 09:55:12 +0100 [thread overview]
Message-ID: <4EF2F070.3020601@broadcom.com> (raw)
In-Reply-To: <CACna6rxEjQLj_j-f7WZOtOEGfDa+TPWyLDrn2t-FGZ5T2_fz-g@mail.gmail.com>
On 12/21/2011 07:52 PM, Rafał Miłecki wrote:
> 2011/12/21 Arend van Spriel <arend@broadcom.com>:
>>
>> The bcm4331 support in b43 is pretty new so I do not expect distros are
>> providing packages for it. Your best bet is to get linux-firmware repo
>> from git.kernel.org. Probably the b43 developers can point you to the
>> specific firmware file you need to use for that phy.
>
> Arend: I'm not sure how to say it nice... but there is only one
> company starting with "B" having copyrights to the BCM4331 firmware.
> Only this company can legally submit BCM4331 firmware to
> linux-firmware repo.
>
Hi Rafał,
That is nicely said and absolutely right. Sorry about that.
Gr.AvS
next prev parent reply other threads:[~2011-12-22 8:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 10:59 bcm4331 firmware installer package lina
2011-12-21 17:38 ` Arend van Spriel
2011-12-21 18:52 ` Rafał Miłecki
2011-12-22 6:57 ` lina
2011-12-22 7:07 ` Rafał Miłecki
2011-12-22 7:47 ` lina
2011-12-22 7:57 ` lina
2011-12-22 8:09 ` lina
2011-12-22 8:34 ` Rafał Miłecki
2011-12-22 8:45 ` lina
2011-12-22 8:49 ` Rafał Miłecki
2011-12-22 8:57 ` lina
2011-12-22 9:09 ` lina
[not found] ` <CANDQx1q8cZC8Qz366ET3XQrpAeVJDiurFFiR1NUQ6G0b_ASoZA@mail.gmail.com>
2012-01-17 20:12 ` Fwd: " Buck Golemon
2011-12-22 8:55 ` Arend van Spriel [this message]
2011-12-21 18:01 ` 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=4EF2F070.3020601@broadcom.com \
--to=arend@broadcom.com \
--cc=b43-dev@lists.infradead.org \
--cc=debian-user@lists.debian.org \
--cc=lina.lastname@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=noelamac@gmail.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 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).