linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	<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, 7 Mar 2017 14:00:38 +0300	[thread overview]
Message-ID: <e5b07c06-740c-cb41-8b92-c4077390ab4c@quantenna.com> (raw)
In-Reply-To: <CACna6rywOG+x7eEaj3-hfUrm8rYdLV38xGFO_JeV0GzvjU6Tvw@mail.gmail.com>

On 03/07/2017 01:45 PM, Rafał Miłecki wrote:
>
> External Email
>
>
> On 7 March 2017 at 11:07, Igor Mitsyanko
> <igor.mitsyanko.os@quantenna.com> wrote:
>> On 03/07/2017 12:19 AM, Rafał Miłecki wrote:
>>> On 01/09/2017 10:07 AM, igor.mitsyanko.os@quantenna.com wrote:
>>>>
>>>> From: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
>>>>
>>>> This patch adds support for new FullMAC WiFi driver for Quantenna
>>>> QSR10G chipsets.
>>>>
>>>> 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
>>>
>>>
>>> Hi, what's the state of this patch? Kalle I see it in your pending branch,
>>> could you give me/us a hint what does it mean, please?
>>
>>
>> Hi Rafal, we will be submitting V5 soon addressing your comments and adding
>> option to "boot from internal flash" rather then from PCIe.
>>
>>>
>>> I've also one not-strictly-related question. What about other chipsets
>>> support?
>>> I'm mostly interested in QT3840BC which can be found in few home routers
>>> that
>>> OpenWrt/LEDE could support.
>>> Can they be supported with submitted core code and just an additional bus
>>> driver?
>>
>>
>> Yes, this is a previous generation SoC, we already have support for those
>> with additional bus driver which we plan to submit as a followup patch,
>> after first one is accepted.
>> But support is only for SoCs' connected with host system over PCIe bus, I'm
>> not sure which product you're interested in exactly: if it uses RGMII
>> interface to interface QT3840BC with host CPU then it basically looks like a
>> simple ETH to host. Not much we can do to support FullMAC driver in this
>> case.
>
> I was interested in supporting ASUS RT-AC87U and maybe Netgear R7500.
>
> According to the https://wikidevi.com/wiki/ASUS_RT-AC87U ASUS indeed
> uses some RGMII interface, I'll need to look for more details first.
> Thanks for looking at this.
>

Yes, looks like it uses RGMII for Quantenna SoC. In theory I think even 
in this case it should be relatively easy to support FullMAC driver by 
implementing one more bus driver that has to use special types of 
ETHERNET frames to implement communication between host CPU and 
Quantenna CPU over RGMII link (using RAW sockets). In this case it will 
look like proxying of cfg80211 requests from host system to any other 
system in the same network L2 domain (addressable by MAC).
But I don't think this approach can ever be upstreamed.

  reply	other threads:[~2017-03-07 11:34 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 [this message]
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
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=e5b07c06-740c-cb41-8b92-c4077390ab4c@quantenna.com \
    --to=igor.mitsyanko.os@quantenna.com \
    --cc=avinashp@quantenna.com \
    --cc=btherthala@quantenna.com \
    --cc=dlebed@quantenna.com \
    --cc=hwang@quantenna.com \
    --cc=johannes@sipsolutions.net \
    --cc=krath@quantenna.com \
    --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).