From: Greg KH <gregkh@suse.de>
To: Rafa?? Mi??ecki <zajec5@gmail.com>
Cc: Henry Ptasinski <henryp@broadcom.com>,
Brett Rudley <brudley@broadcom.com>,
Nohee Ko <noheek@broadcom.com>,
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: Mon, 18 Oct 2010 17:30:00 -0700 [thread overview]
Message-ID: <20101019003000.GA28348@suse.de> (raw)
In-Reply-To: <AANLkTin_JcEyT21dTS=Ew868HJvZQ2FVZBGXjCZn=8O_@mail.gmail.com>
On Tue, Oct 19, 2010 at 02:02:06AM +0200, Rafa?? Mi??ecki wrote:
> W dniu 9 pa??dziernika 2010 00:07 u??ytkownik Rafa?? Mi??ecki
> <zajec5@gmail.com> napisa??:
> > Hi Broadcom fellows!
> >
> > It's great that afters long years of... well, pretty horrible
> > relations with Linux/opensource you have taken actions to change your
> > image. I guess brcm80211 it's perfect yet, and people may like it more
> > or less, but it's no doubt you made step in the right direction.
> > Thanks for that!
> >
> > As you should know, you released driver and firmware for 802.11n
> > devices only. I believe it was right, as these device seem to be the
> > most nowadays and were the only ones without any open source support.
> > For older devices: G-PHY and LP-PHY we have working b43 driver that is
> > in relatively good shape. However... there is one thing we still miss
> > for olders cards.
> >
> > Every time someone wants to use b43 it's necessary to download quite
> > big package from openwrt, unpack it, extract firmware and install it.
> > That simply happens because we don't have just-firmware files with
> > nice licensing. And of course there goes my request:
> >
> > *Can you submit G-PHY and LP-PHY firmware to linux-firmware using some
> > normal licensing, please?*
> >
> > This is of course not the best I could wish for, but is important
> > anyway and it should be easy decision. Ideally you could release
> > sources of firmware (plus toolchain eventualy... however, we have nice
> > toolchain from Michael), but I guess it would need more time and
> > decisions to make it happen. So as for now I guess we would be happy
> > with just closed source but easy-distributable firmware. Could you
> > release, submit it?
>
> Greg: I didn't receive any answer from Broadcom for any mail. Do you
> maybe have any "working" contact with this company? :|
Heh, no, Henry and the others on the cc: above are all I have.
Hopefully they will be able to reply, or at least give us a "we are not
the developers/people who can help out with this, but please try these
other email addresses..."
Henry?
thanks,
greg k-h
next prev parent reply other threads:[~2010-10-19 0:46 UTC|newest]
Thread overview: 14+ 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
2010-10-19 0:30 ` Greg KH [this message]
2010-10-20 21:50 ` Henry Ptasinski
2010-10-20 22:11 ` Rafał Miłecki
2010-10-20 22:13 ` Luis R. Rodriguez
2010-10-21 15:21 ` Dan Williams
2011-02-18 21:24 ` Rafał Miłecki
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: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=20101019003000.GA28348@suse.de \
--to=gregkh@suse.de \
--cc=b43-dev@lists.infradead.org \
--cc=brudley@broadcom.com \
--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 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).