All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: igor.mitsyanko.os@quantenna.com
Cc: linux-firmware@kernel.org, linux-wireless@vger.kernel.org,
	Igor Mitsyanko <imitsyanko@quantenna.com>,
	Kamlesh Rath <krath@quantenna.com>,
	Sergey Matyukevich <smatyukevich@quantenna.com>,
	Avinash Patil <avinashp@quantenna.com>
Subject: Re: [RFC] qtn: add FullMAC firmware for Quantenna QSR10G wifi device
Date: Fri, 23 Dec 2016 18:47:22 +0100	[thread overview]
Message-ID: <1796267.ZQn77y5fxL@debian64> (raw)
In-Reply-To: <1482505955-9310-1-git-send-email-igor.mitsyanko.os@quantenna.com>

On Friday, December 23, 2016 6:12:35 PM CET igor.mitsyanko.os@quantenna.com wrote:
> From: Igor Mitsyanko <imitsyanko@quantenna.com>
> 
> QSR10G is Quantenna's 8x8, 160M, 11ac WiFi card.
> 
> Signed-off-by: Kamlesh Rath <krath@quantenna.com>
> Signed-off-by: Sergey Matyukevich <smatyukevich@quantenna.com>
> Signed-off-by: Avinash Patil <avinashp@quantenna.com>
> Signed-off-by: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
> ---
> This is an RFC patch that we sent to linux-wireless mailing list a while ago,
> and it spawned a discussion regarding whether GPL sources has to be submitted
> together with this firmware. We would like to clarify with linux-firmware maintainers
> to understnad what should be our actions to allow this to be accepted.
> - firmware contains GPL components;
> - LICENCE file states that sources for GPL components will be provided on request
> to oslegal@quantenna.com
> 
> There was an opinion that it is not enough: precedent case like this with carl9170
> firmware was resolved by submitting GPL sources into linux-firmware repository
> itself.
The ar9170-usb firmware was released as GPL v2.0 from the get-go.
<http://git.sipsolutions.net/ar9170-fw.git/commit/GPL?id=2e3574ce10c74a82047a06b046855de14d969948>

And this was never a problem. What is THE PROBLEM though:
"if all the patches from ar9170fw to carl9170fw and beyond (i.e new versions)
have to be added to linux-firmware.git." Or not.

That's why there was never a update to the carl9170fw.
So be prepared for this scenario too.

> Does the same applies to qsr10g firmware?
>
> The SDK that we use to build it is quite heavy (> 100MB, but with toolchain). 
> Maybe we can take another approach to place SDK separately on Quantenna website
> (as a compressed archive), and add a link in linux-firmware?
Yes, I would like to know this as well.

Regards,
Christian

  reply	other threads:[~2016-12-23 17:47 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
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 [this message]
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=1796267.ZQn77y5fxL@debian64 \
    --to=chunkeey@googlemail.com \
    --cc=avinashp@quantenna.com \
    --cc=igor.mitsyanko.os@quantenna.com \
    --cc=imitsyanko@quantenna.com \
    --cc=krath@quantenna.com \
    --cc=linux-firmware@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --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.