From: Johannes Berg <johannes@sipsolutions.net>
To: "Igor Mitsyanko" <igor.mitsyanko.os@quantenna.com>,
"Arend Van Spriel" <arend.vanspriel@broadcom.com>,
"Kalle Valo" <kvalo@codeaurora.org>,
"Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, btherthala@quantenna.com,
hwang@quantenna.com, smaksimenko@quantenna.com,
dlebed@quantenna.com,
Sergey Matyukevich <smatyukevich@quantenna.com>,
Kamlesh Rath <krath@quantenna.com>,
Avinash Patil <avinashp@quantenna.com>
Subject: Re: [PATCH v4] qtnfmac: announcement of new FullMAC driver for Quantenna chipsets
Date: Tue, 14 Mar 2017 15:03:40 +0100 [thread overview]
Message-ID: <1489500220.10872.8.camel@sipsolutions.net> (raw)
In-Reply-To: <6be6c73d-381b-6579-8b57-2a836973b446@quantenna.com>
> 1. Modify cfg80211 driver patch to introduce ability to boot from
> card's
> internal flash rather then over PCIe only. This will hopefully
> unblock
> driver itself.
This is good, and I think that'll be OK for the driver.
> 2. Work internally to provide access to SDK used to build firmware on
> a
> public server, that has to be accessible for two years. Then submit
> firmware to linux-firmware again.
I'm not sure this will work, since it would fall on anyone
redistributing to ensure it's still there after *they* distribute it,
so anyone who has the linux-firmware repo... That's why it's most
practical to simply combine the two, although that's not really the
case here.
johannes
next prev parent reply other threads:[~2017-03-14 14:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 9:07 [PATCH v4] qtnfmac: announcement of new FullMAC driver for Quantenna chipsets igor.mitsyanko.os
2017-03-06 21:19 ` Rafał Miłecki
2017-03-07 10:07 ` Igor Mitsyanko
2017-03-07 10:45 ` Rafał Miłecki
2017-03-07 11:00 ` Igor Mitsyanko
2017-03-07 13:03 ` Julian Calaby
2017-03-07 13:39 ` Kalle Valo
2017-03-08 9:10 ` Arend Van Spriel
2017-03-09 9:58 ` Igor Mitsyanko
2017-03-14 14:03 ` Johannes Berg [this message]
2017-03-16 7:50 ` Kalle Valo
2017-03-06 21:25 ` Rafał Miłecki
2017-03-07 10:17 ` Igor Mitsyanko
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=1489500220.10872.8.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=avinashp@quantenna.com \
--cc=btherthala@quantenna.com \
--cc=dlebed@quantenna.com \
--cc=hwang@quantenna.com \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=krath@quantenna.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=smaksimenko@quantenna.com \
--cc=smatyukevich@quantenna.com \
--cc=zajec5@gmail.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).