From: Erik Stromdahl <erik.stromdahl@gmail.com>
To: jay@systech.com, ath10k@lists.infradead.org
Subject: Re: QCA9377 USB Support
Date: Wed, 8 Nov 2017 21:37:33 +0100 [thread overview]
Message-ID: <79b74837-52d4-016f-b0ee-20662a2acc05@gmail.com> (raw)
In-Reply-To: <258cab35-9a7c-700d-8115-d599ced0f850@systech.com>
Hi Jay,
On 2017-11-06 23:21, Jay Foster wrote:
> I am looking for linux driver support for the QCA9377 USB Wi-Fi device (0cf3:9378). I see on the mailing list archives that a patch (https://marc.info/?l=linux-wireless&m=150567724712332&w=2) to add this to the ath10k driver was posted on September 17, 2017. According to the ath10k sources documentation (https://wireless.wiki.kernel.org/en/users/drivers/ath10k/sources) such patches usually take a couple of weeks to get committed to either the master or ath-next branch of the kvalo ath.git tree. I cloned the tree, but do not see this patch there on any branches.
>
> What is the status of support for the QCA9377 USB device using ath10k?
Parts of the USB support have been added to the ath.git repo and to mainline (but not the patch you were referring to (as you noticed yourself)).
However, the patches are available here:
https://github.com/erstrom/linux-ath
Current status:
https://github.com/erstrom/linux-ath/wiki
--
Erik
>
> Jay
>
>
>
>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-11-08 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 22:21 QCA9377 USB Support Jay Foster
2017-11-08 20:37 ` Erik Stromdahl [this message]
2017-11-21 8:01 ` Kalle Valo
2018-01-09 0:02 ` Jay Foster
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=79b74837-52d4-016f-b0ee-20662a2acc05@gmail.com \
--to=erik.stromdahl@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=jay@systech.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