Return-path: Received: from s3.sipsolutions.net ([5.9.151.49]:54558 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752395AbcKKLfx (ORCPT ); Fri, 11 Nov 2016 06:35:53 -0500 Message-ID: <1478864146.4129.4.camel@sipsolutions.net> (sfid-20161111_123557_329089_97732DE0) Subject: Re: [RFC] qtn: add FullMAC firmware for Quantenna QSR10G wifi device From: Johannes Berg To: IgorMitsyanko Cc: linux-wireless@vger.kernel.org, btherthala@quantenna.com, hwang@quantenna.com, smaksimenko@quantenna.com, dlebed@quantenna.com, Igor Mitsyanko , Kamlesh Rath , Sergey Matyukevich , Avinash Patil , Ben Hutchings , Kyle McMartin Date: Fri, 11 Nov 2016 12:35:46 +0100 In-Reply-To: References: <1478700000-11624-1-git-send-email-igor.mitsyanko.os@quantenna.com> <1478706966.18306.1.camel@sipsolutions.net> <2fcb5f28-808e-f296-7e91-e5185e7577c9@quantenna.com> <1478725543.21403.4.camel@sipsolutions.net> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: 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