From: "Rafał Miłecki" <zajec5@gmail.com>
To: Henry Ptasinski <henryp@broadcom.com>
Cc: Greg KH <greg@kroah.com>, David Woodhouse <dwmw2@infradead.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
Brett Rudley <brudley@broadcom.com>,
"grundler@google.com" <grundler@google.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Roland Vossen <rvossen@broadcom.com>,
Dowan Kim <dowan@broadcom.com>,
Arend Van Spriel <arend@broadcom.com>,
dcbw@redhat.com
Subject: Re: [PATCH v2] linux-firmware: brcm: Removed codeversion from firmware filenames.
Date: Thu, 9 Dec 2010 01:28:31 +0100 [thread overview]
Message-ID: <AANLkTimXjLCLwznMDzT-KdX1qfHvdbpNpJPcNpmuZkOS@mail.gmail.com> (raw)
In-Reply-To: <20101208233527.GA2148@broadcom.com>
2010/12/9 Henry Ptasinski <henryp@broadcom.com>:
> On Wed, Dec 08, 2010 at 02:23:49PM -0800, Greg KH wrote:
>> On Wed, Dec 08, 2010 at 11:07:53PM +0100, Rafał Miłecki wrote:
>> > 2010/12/8 Henry Ptasinski <henryp@broadcom.com>:
>> > > Second attempt at cleaning up firmware filenames.
>> > >
>> > > The basename-apiversion-codeversion construction for firmware filenames is not
>> > > used by most other firmware files, adds complexity, and is not providing any
>> > > value. Renamed the firmware files using just basename-apiversion. Also, fixed
>> > > WHENCE to have correct path to brcmfmac files.
>> > >
>> > > Signed-off-by: Henry Ptasinski <henryp@broadcom.com>
>> >
>> > Henry, I believe we got report that Red Hat can not include your
>> > firmware anyway because of licensing. Can you change license to some
>> > common one which allows providing your firmware with distributions?
>>
>> That's news to me, what specific licensing issue have you heard about
>> here? Last I saw, the issues were resolved and everyone could
>> redistribute this firmware.
>
> On a thread about other firmware, Dan Williams wrote:
>
>> 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.
>
> I'm not sure that translates to "can not include your firmware". Regardless, I
> am trying to get our license simplified. Obviously that's taking some time,
> and I don't have any resolution yet, but I'll keep working on it.
You quoted just a selected part of Dan's message. Earlier he mentioned
about Fedora's problems (sorry, I misremembered distro)
---------- Wiadomość przekazana dalej ----------
Od: Dan Williams <dcbw@redhat.com>
Data: 21 października 2010 17:21
Temat: Re: Request for free-distributable Broadcom's (G|LP)-PHY firmware
Do: Rafał Miłecki <zajec5@gmail.com>
DW: 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>
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.
next prev parent reply other threads:[~2010-12-09 0:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4CBE23F4.4020104@broadcom.com>
[not found] ` <20101019233520.GA12510@kroah.com>
[not found] ` <FD96C117992C584DBC47231B1EB6F5568206D859DC@SJEXCHCCR02.corp.ad.broadcom.com>
[not found] ` <20101020004743.GB31965@kroah.com>
[not found] ` <20101020005546.GL10832@broadcom.com>
[not found] ` <20101020010320.GA370@kroah.com>
2010-10-20 2:18 ` [PATCH] staging:brcm80211:brcmfmac:change firmware/config file name Henry Ptasinski
2010-10-20 3:10 ` Greg KH
2010-10-20 11:49 ` Rafał Miłecki
2010-10-20 18:04 ` Henry Ptasinski (local)
2010-10-21 17:08 ` [PATCH] linux-firmware: brcm: Removed codeversion from firmware filenames Henry Ptasinski
2010-11-01 14:28 ` David Woodhouse
2010-12-08 20:50 ` [PATCH v2] " Henry Ptasinski
2010-12-08 22:07 ` Rafał Miłecki
2010-12-08 22:23 ` Greg KH
2010-12-08 23:35 ` Henry Ptasinski
2010-12-09 0:28 ` Rafał Miłecki [this message]
2010-12-09 1:30 ` Henry Ptasinski
2010-12-09 9:01 ` Rafał Miłecki
2010-10-21 17:10 ` Subject: [PATCH] staging: brcm80211: brcmfmac: " Henry Ptasinski
2010-10-21 18:26 ` Greg KH
2010-10-21 18:37 ` Subject: [PATCH v2] " Henry Ptasinski
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=AANLkTimXjLCLwznMDzT-KdX1qfHvdbpNpJPcNpmuZkOS@mail.gmail.com \
--to=zajec5@gmail.com \
--cc=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=dcbw@redhat.com \
--cc=devel@linuxdriverproject.org \
--cc=dowan@broadcom.com \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=grundler@google.com \
--cc=henryp@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rvossen@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).