From: Kalle Valo <kvalo@kernel.org>
To: Wim Van Boven <wimvanboven@gmail.com>
Cc: ath11k <ath11k@lists.infradead.org>
Subject: Re: support for WCN6855 liteon subsystem device 11ad:a82d
Date: Fri, 06 May 2022 09:38:35 +0300 [thread overview]
Message-ID: <87bkwb9ndg.fsf@kernel.org> (raw)
In-Reply-To: <6VYEBR.N4O0Q6H2MTME3@gmail.com> (Wim Van Boven's message of "Thu, 05 May 2022 16:28:18 +0200")
Wim Van Boven <wimvanboven@gmail.com> writes:
> the firmware doesn't have the board information for this
> subsystem-device:
>
> 02:00.0 Network controller [0280]: Qualcomm Atheros QCNFA765
> [17cb:1103] (rev 01)
> Subsystem: Lite-On Communications Inc Device [11ad:a82d]
>
> however, it seems to work fine with this one:
> bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=9409,qmi-chip-id=18,qmi-board-id=255m
>
> i hexedited the board-2.bin and swapped out the vendor and device
> identifiers to match the LiteOn ones, which seems to work properly,
> but is likely not the proper way to do this.
BTW we have a tool for creating board-2.bin so that you don't need to
use hexedit:
https://github.com/qca/qca-swiss-army-knife/blob/master/tools/scripts/ath11k/ath11k-bdencoder
Unfortunately no documentation but hopefully --help provides some guidance.
> what would be the proper way to get support for this device and how
> can i help?
Can you report this to bugzilla.kernel.org:
https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport
That way it's easier to track. I'll try to find a board file for this
device.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2022-05-06 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 14:28 support for WCN6855 liteon subsystem device 11ad:a82d Wim Van Boven
2022-05-06 6:38 ` Kalle Valo [this message]
2022-05-06 8:20 ` Kalle Valo
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=87bkwb9ndg.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=wimvanboven@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