From: Ben Hutchings <ben@decadent.org.uk>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
ath10k@lists.infradead.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH 3/3] ath10k: add firmware files
Date: Sun, 16 Mar 2014 18:57:10 +0000 [thread overview]
Message-ID: <1394996230.15764.113.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <CAB=NE6WW8yX4kdy02j2fT4g0JvYj4a_XkiqYtXKZSMB7FHuwNg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]
On Fri, 2014-03-14 at 05:36 -0700, Luis R. Rodriguez wrote:
> On Fri, Mar 14, 2014 at 1:45 AM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
[...]
> > + NO LICENSES OR OTHER RIGHTS,
> > +WHETHER EXPRESS, IMPLIED, BASED ON ESTOPPEL OR OTHERWISE, ARE GRANTED
> > +TO ANY PARTY'S PATENTS, PATENT APPLICATIONS, OR PATENTABLE INVENTIONS
> > +BY VIRTUE OF THIS LICENSE OR THE DELIVERY OR PROVISION BY QUALCOMM
> > +ATHEROS, INC. OF THE SOFTWARE.
>
> This -- however is new to linux-firmware -- and I hereby raise a big
> red fucking flag. All other licenses on linux-firmware provide at the
> very least a limited patent grant. What makes Qualcomm special ?
[...]
There are several licence texts that don't mention patents at all. I'm
assuming that the companies submitting firmware for inclusion in Linux
or linux-firmware do intend to grant whatever licences are required to
distribute it to end users.
Several licence texts explicitly exclude patent licences relating to any
*other* products of the same company, but that's quite redundant.
However this language seems to explicitly exclude *any* patent licence.
You're right to raise a red flag because, assuming Qualcomm does have
patents that cover the firmware alone, this seems to disallow
redistribution in whatever jurisdictions those patents apply.
Ben.
--
Ben Hutchings
Computers are not intelligent. They only think they are.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2014-03-16 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140314084501.23100.13103.stgit@x230>
[not found] ` <20140314084514.23100.72654.stgit@x230>
2014-03-14 12:36 ` Luis R. Rodriguez
2014-03-14 12:47 ` Dave Taht
2014-03-14 15:23 ` Arend van Spriel
2014-03-14 17:07 ` Kalle Valo
2014-03-14 17:25 ` Luis R. Rodriguez
2014-03-16 18:57 ` Ben Hutchings [this message]
2014-03-16 20:17 ` Luis R. Rodriguez
2014-06-25 15:47 ` Luis R. Rodriguez
2014-03-17 8:45 ` Alex Hacker
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=1394996230.15764.113.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=ath10k@lists.infradead.org \
--cc=dwmw2@infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®