From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: ath10k@lists.infradead.org
Cc: Chris Blake <chrisrblake93@gmail.com>, Kalle Valo <kvalo@codeaurora.org>
Subject: ath10k-firmware: QCA4019 hw1.0: Add Meraki MR33 specific BDFs
Date: Tue, 17 Apr 2018 10:15:29 +0200 [thread overview]
Message-ID: <1756157.Q00gyP1f8V@bentobox> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1427 bytes --]
Hi,
The support for this device was added a while ago to OpenWrt. This AP requires
two special BDFs to get the Wi-Fi PHYs working (correctly). The bmi-board-
id='s would clash with one of the the IPQ401X AP-DK boards because QCA doesn't
provide special IDs for customers and seems to use the AP-DK board-ids in the
wifi firmware to change its behavior.
Now to the questions from the wiki page [1]:
* description for what hardware this is:
- it is a IPQ4029 based board
- one QCA40xx radio is used as 2.4GHz radio
- one QCA40xx radio is used as 5GHz radio
* origin of the board file (did you create it yourself or where you
downloaded)
- Chris didn't include this info in the OpenWrt commit (maybe he can add it
here)
- most likely taken from stock firmware image
* ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k)
- QCA4019 hw1.0
+ bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=Meraki-MR33
sha256sum:
44e8e733d5fc9bd747520d492c776a6fa4cd7effed69098aeb6f9d437785ebad
+ bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=Meraki-MR33
sha256sum:
e816565130fae895cfa0c1760cfb47703f1bc5f24ce87922f86e94d4e2b6ccd2
* attach the actual board file (board.bin)
- The name of the files are equal to the id string in the board-2.bin
(minus the ".bin")
Kind regards,
Sven
[1] https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles
[-- Attachment #1.1.2: bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=Meraki-MR33.bin --]
[-- Type: application/octet-stream, Size: 12064 bytes --]
[-- Attachment #1.1.3: bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=Meraki-MR33.bin --]
[-- Type: application/octet-stream, Size: 12064 bytes --]
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2018-04-17 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 8:15 Sven Eckelmann [this message]
2018-04-17 15:04 ` ath10k-firmware: QCA4019 hw1.0: Add Meraki MR33 specific BDFs Chris Blake
2018-04-18 16:56 ` Kalle Valo
2018-04-19 6:40 ` Sven Eckelmann
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=1756157.Q00gyP1f8V@bentobox \
--to=sven.eckelmann@openmesh.com \
--cc=ath10k@lists.infradead.org \
--cc=chrisrblake93@gmail.com \
--cc=kvalo@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox