All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: IgorMitsyanko <igor.mitsyanko.os@quantenna.com>
Cc: linux-wireless@vger.kernel.org, btherthala@quantenna.com,
	hwang@quantenna.com, smaksimenko@quantenna.com,
	dlebed@quantenna.com, Igor Mitsyanko <imitsyanko@quantenna.com>,
	Kamlesh Rath <krath@quantenna.com>,
	Sergey Matyukevich <smatyukevich@quantenna.com>,
	Avinash Patil <avinashp@quantenna.com>,
	Ben Hutchings <ben@decadent.org.uk>,
	Kyle McMartin <kyle@kernel.org>
Subject: Re: [RFC] qtn: add FullMAC firmware for Quantenna QSR10G wifi device
Date: Fri, 11 Nov 2016 12:35:46 +0100	[thread overview]
Message-ID: <1478864146.4129.4.camel@sipsolutions.net> (raw)
In-Reply-To: <d1cfaf8a-55a6-3a7c-9e9d-ec810fe5b80d@quantenna.com>

Adding linux-firmware people to Cc, since presumably they don't
necessarily read linux-wireless...

> Johannes, from that perspective, who are the "redistributors"? 

> Specifically, is linux-firmware git repository considered a
> redistributor or its just hosting files? I mean, at what moment
> someone else other then Quantenna will start to be legally obliged to
> make GPL code used in firmware available for others?

Look, I don't know. I'd assume people who ship it, like any regular
distro, would be (re)distributors thereof. "Normal" (non-GPL) firmware
images come with a redistribution license, but that obviously can't
work here.

There's some info from Ben here regarding the carl9170 case:
http://lkml.iu.edu/hypermail/linux/kernel/1605.3/01176.html

> Personally I still hope that linux-firmware itself is not legally 
> concerned with what is the content of firmware its hosting, but looks
> like there already was a precedent case  with carl9170 driver and
> we have to somehow deal with it.

That's really all I wanted to bring up. I'm not involved with the
linux-firmware git tree.

> There still may be a difference though: Quantenna is semiconductor 
> company only, software
> used on actual products based on Quantenna chipsets is released by
> other 
> companies.
> I just want to present our legal team with a clear case (and position
> of 
> Linux maintainers) so that they can
> work with it and make decision on how to proceed.
> 
>  From technical perspective, as I mentioned, SDK is quite huge and 
> include a lot of opensource
> components including full Linux, I don't think its reasonable to have
> it 
> inside linux-firmware tree.
> What are the options to share it other then providing it on request
> basis:
> - git repository
> - store tarball somewhere on official website

Clearly that wasn't deemed appropriate for carl9170, so I don't see why
it'd be different here.

johannes

  reply	other threads:[~2016-11-11 11:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1478700000-11624-1-git-send-email-igor.mitsyanko.os@quantenna.com>
2016-11-09 14:00 ` [PATCH V3] qtnfmac: announcement of new FullMAC driver for Quantenna chipsets igor.mitsyanko.os
2016-11-14  9:52   ` Johannes Berg
     [not found]     ` <62102ba6-cae0-f00d-f989-3f2e9ea43d9b@quantenna.com>
2016-11-16 16:50       ` IgorMitsyanko
2016-11-17  8:51         ` Johannes Berg
2016-11-15  9:06   ` Johannes Berg
2016-11-16 16:47     ` IgorMitsyanko
2016-11-17  7:54       ` Johannes Berg
2016-11-09 15:56 ` [RFC] qtn: add FullMAC firmware for Quantenna QSR10G wifi device Johannes Berg
     [not found]   ` <2fcb5f28-808e-f296-7e91-e5185e7577c9@quantenna.com>
2016-11-09 21:05     ` Johannes Berg
2016-11-10 14:02       ` IgorMitsyanko
2016-11-11 11:35         ` Johannes Berg [this message]
2016-11-14  8:26           ` IgorMitsyanko
2016-11-14  9:40             ` Johannes Berg
2016-11-23 15:25             ` Kalle Valo
2016-11-23 16:45               ` igor.mitsyanko.os
2016-11-23 17:09               ` IgorMitsyanko
2016-11-24 11:59                 ` Kalle Valo
2016-11-25 10:16                   ` IgorMitsyanko
2016-12-23 15:12               ` igor.mitsyanko.os
2016-12-23 17:47                 ` Christian Lamparter
2016-11-22 14:44           ` IgorMitsyanko
2016-11-28 16:34             ` Kyle McMartin
2016-11-28 17:10               ` Oleksij Rempel
2016-11-28 17:33                 ` Oleksij Rempel
2016-11-28 19:01                   ` IgorMitsyanko
2016-11-29  3:49                     ` Oleksij Rempel
2016-11-29  9:10                       ` IgorMitsyanko
2016-11-29  9:34                         ` Arend Van Spriel
2016-11-29 10:22                           ` IgorMitsyanko
2016-11-28 22:07               ` IgorMitsyanko

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=1478864146.4129.4.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=avinashp@quantenna.com \
    --cc=ben@decadent.org.uk \
    --cc=btherthala@quantenna.com \
    --cc=dlebed@quantenna.com \
    --cc=hwang@quantenna.com \
    --cc=igor.mitsyanko.os@quantenna.com \
    --cc=imitsyanko@quantenna.com \
    --cc=krath@quantenna.com \
    --cc=kyle@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=smaksimenko@quantenna.com \
    --cc=smatyukevich@quantenna.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.