From: Kalle Valo <kvalo@codeaurora.org>
To: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
Cc: <linux-wireless@vger.kernel.org>, <johannes@sipsolutions.net>,
Dmitrii Lebed <dlebed@quantenna.com>,
Sergei Maksimenko <smaksimenko@quantenna.com>,
Sergey Matyukevich <smatyukevich@quantenna.com>,
Bindu Therthala <btherthala@quantenna.com>,
Huizhao Wang <hwang@quantenna.com>,
Kamlesh Rath <krath@quantenna.com>,
Avinash Patil <avinashp@quantenna.com>
Subject: Re: [PATCH v5] qtnfmac: announcement of new FullMAC driver for Quantenna chipsets
Date: Tue, 09 May 2017 18:04:19 +0300 [thread overview]
Message-ID: <878tm69imk.fsf@purkki.adurom.net> (raw)
In-Reply-To: <c80e4171-d433-6f31-f279-94aa5d238dc7@quantenna.com> (Igor Mitsyanko's message of "Fri, 28 Apr 2017 00:22:40 -0700")
Igor Mitsyanko <igor.mitsyanko.os@quantenna.com> writes:
> On 03/11/2017 12:04 PM, Igor Mitsyanko wrote:
>> This patch adds support for new FullMAC WiFi driver for Quantenna
>> QSR10G chipsets.
>
> Hi all,
> this patch is pending for a while now, does it require more work
> (except for what Christian mentioned)?
I just did a diff between v4 and v5 and looking good at least to me. Do
others have more comments/concerns?
Now would be a very good time to submit a new driver as we are getting
close to the rc1 release. This way it gets plenty of testing time in
linux-next. So sooner you can submit v6 the better.
>> QSR10G (aka Pearl) is Quantenna's 8x8, 160M, 11ac offering.
>> QSR10G supports 2 simultaneous WMACs - one 5G and one 2G.
>> 5G WMAC supports 160M, 8x8 configuration. FW supports
>> up to 8 concurrent virtual interfaces on each WMAC.
>>
>> Patch introduces 2 new drivers:
>> - qtnfmac.ko for interfacing with kernel wireless core
>> - qtnfmac_pearl_pcie.ko for interfacing with hardware over PCIe interface
Please mention in the commit log also what modes (AP, managed, monitor
etc) are supported.
But PLEASE edit your quotes, the insane 8000 line quote makes my use of
patchwork[1] difficult:
https://patchwork.kernel.org/patch/9619075/
[1] And I do almost all of my maintainer work via patchwork so this
habit of not editing quotes is a big hindrance for me. And
unfortunately it's getting more popular :(
--
Kalle Valo
next prev parent reply other threads:[~2017-05-09 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 20:04 [PATCH v5] qtnfmac: announcement of new FullMAC driver for Quantenna chipsets Igor Mitsyanko
2017-03-12 16:59 ` Christian Lamparter
2017-03-13 10:24 ` Igor Mitsyanko
2017-04-28 7:22 ` Igor Mitsyanko
2017-05-09 15:04 ` Kalle Valo [this message]
2017-05-09 15:07 ` Kalle Valo
2017-05-09 22:23 ` 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=878tm69imk.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--cc=avinashp@quantenna.com \
--cc=btherthala@quantenna.com \
--cc=dlebed@quantenna.com \
--cc=hwang@quantenna.com \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=johannes@sipsolutions.net \
--cc=krath@quantenna.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox