From: Kalle Valo <kvalo@kernel.org>
To: Wenli Looi <wlooi@ucalgary.ca>
Cc: ath9k-devel@qca.qualcomm.com,
Miaoqing Pan <miaoqing@codeaurora.org>,
linux-wireless@vger.kernel.org
Subject: Re: QCN5502 support in ath9k
Date: Tue, 08 Feb 2022 13:08:55 +0200 [thread overview]
Message-ID: <87r18d1upk.fsf@kernel.org> (raw)
In-Reply-To: <CAKe_nd1jthFhJhojQLXMeU741AoTks74K+J1v5FqS6ABB6gW-Q@mail.gmail.com> (Wenli Looi's message of "Tue, 8 Feb 2022 02:21:18 -0800")
Wenli Looi <wlooi@ucalgary.ca> writes:
> I'm wondering if there's any plan to support QCN5502 in ath9k. If not,
> is it possible to obtain the initvals and other information that would
> be required to support QCN5502 in ath9k? (such as those for QCA956x in
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath9k/ar956x_initvals.h)
>
>
> For context, I have recently submitted two patches that seem to allow
> QCN5502 to be fully functional except for the integrated wifi:
>
> * https://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/commit/?id=a0b8cd5c223042efe764864b8dd9396ee127c763
>
> * https://github.com/openwrt/openwrt/pull/4271
>
> Thanks!
Don't use HTML, linux-wireless drops all HTML mail, I don't know about
QCN5502 support, but hopefully people see your email now.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next parent reply other threads:[~2022-02-08 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKe_nd1jthFhJhojQLXMeU741AoTks74K+J1v5FqS6ABB6gW-Q@mail.gmail.com>
2022-02-08 11:08 ` Kalle Valo [this message]
2022-03-09 22:38 ` QCN5502 support in ath9k Wenli Looi
2022-03-09 23:24 ` Toke Høiland-Jørgensen
2022-03-11 1:55 ` Wenli Looi
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=87r18d1upk.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=miaoqing@codeaurora.org \
--cc=wlooi@ucalgary.ca \
/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).