From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: David Hutchison <dhutchison@bluemesh.net>,
OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [OpenWrt-Devel] How to initialize multiple phy radios
Date: Mon, 25 Apr 2016 15:21:45 +0000 [thread overview]
Message-ID: <87potd3e9j.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <2596438.Cv6xmiar05@debian64> (Christian Lamparter's message of "Sun, 24 Apr 2016 12:48:39 +0200")
Christian Lamparter <chunkeey@googlemail.com> writes:
> On Sunday, April 24, 2016 01:16:11 AM David Hutchison wrote:
>> I spoke too soon:
>> https://pci-ids.ucw.cz/read/PC/168c/0050
>>
>> It is the QCA9887, so it's definitely on the PCIe bus and is being
>> seen.
>
> Does ath10k support the QCA9887? I see no entry for this pci-id (168c:0050)
> in ath10k's pci table [0] and there's no definition of it in the hardware
> header either [1]. The chip-id is also not present. I CC'ed ath10k, since
> this seems to be a new chip that might be easy to add.
Currently ath10k does not support QCA9887.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-04-25 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+i30h-5GCJ0h9REAJE8TCdxNQDe8Sa=Fs=gbxpHEW3fOY-hMw@mail.gmail.com>
[not found] ` <CA+i30h--nmpjeNK4S02a9o9qrQ-b3QR77WcRorxC5-Dame5hBw@mail.gmail.com>
[not found] ` <CA+i30h-Y_rB0kZfgWifk14Zw1CCkGZH5x5zf8+OH-GTwswXh3w@mail.gmail.com>
2016-04-24 10:48 ` [OpenWrt-Devel] How to initialize multiple phy radios Christian Lamparter
2016-04-25 15:21 ` Valo, Kalle [this message]
2016-04-25 16:53 ` David Hutchison
2016-04-25 19:01 ` Christian Lamparter
2016-04-25 22:14 ` David Hutchison
2016-04-26 7:20 ` Valo, Kalle
2016-04-26 12:21 ` Christian Lamparter
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=87potd3e9j.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=chunkeey@googlemail.com \
--cc=dhutchison@bluemesh.net \
--cc=openwrt-devel@lists.openwrt.org \
/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.