From: Lech Perczak <lech.perczak@gmail.com>
To: ath10k@lists.infradead.org
Subject: ath10k-firmware:: QCA9888 hw2.0: Add ZTE MF286C specific BDF
Date: Sun, 27 Oct 2024 03:28:54 +0100 [thread overview]
Message-ID: <4292f19b-e413-4a0c-9890-e13d6b559c4a@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
Hello,
This device works with OpenWrt, currently using images for MF286A variant,
but wireless interfaces were heavily modified from previous iteration -
- now 2x2 configuration is used instead of 3x3, and without the file,
5GHz performance suffers badly. Replacing generic board data with file
extracted from vendor firmware fixes that.
I would like to upstream the board file for it, before I upstream support for
this variant to OpenWrt, as this will have to be referenced in the device tree
explicitly.
Now to the questions from the wiki page [1]:
* description for what hardware this is:
- it is a QCA9563 based board
- QCA9563 is used for 2.4GHz (so out of concern for ath10k)
- QCA9888 is used for 5GHz band
* origin of the board file (did you create it yourself or where you
downloaded)
- Extracted from the vendor firmware by myself.
* ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k)
- QCA9888 hw2.0
+ bus=pci,bmi-chip-id=0,bmi-board-id=16,variant=ZTE-MF286C.bin
sha256sum:
140a4abbb441a3ad0fb35a7e21c6d5b4034516b77eb232aedfacd2a7d57dad0e
* attach the actual board file (board.bin)
- The name of the file is equal to the id string in the board-2.bin
(minus the ".bin")
With kind regards,
Lech
[1]https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles
[-- Attachment #2: bus=pci,bmi-chip-id=0,bmi-board-id=16,variant=ZTE-MF286C.bin --]
[-- Type: application/octet-stream, Size: 12064 bytes --]
reply other threads:[~2024-10-27 2:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4292f19b-e413-4a0c-9890-e13d6b559c4a@gmail.com \
--to=lech.perczak@gmail.com \
--cc=ath10k@lists.infradead.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.