Skip to contentSkip to conversation

ath10k-firmware: QCA4019 hw1.0: Add Meraki MR33 specific BDFs

DISCUSSION Sven Eckelmann 3 participants 4 messages Apr 17, 2018 – Apr 19, 2018 Qualcomm Atheros ATH10K wireless driver

lore
Share & tools
lore
#0 lore raw

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

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#1 lore raw
Quoted 36 lines · Sven Eckelmann

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)

Quoted 7 lines

- 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

Hello,
For the Meraki MR33, the board file was pulled out of the factory firmware image with assistance from Christian Lamparter, who I have CCd to this thread.

Regards,
Chris Blake

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

#2 lore raw
In reply to Sven Eckelmann
Quoted 32 lines · Sven Eckelmann

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
Quoted 4 lines

* 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")

I added these now, please check that I did it correctly. It's very easy for me to make a mistake.

https://github.com/kvalo/ath10k-firmware/commit/66be3a48d9cf17ace8413cf478a5954483393af4

Signature · 5 lines
Kalle Valo
_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
#3 lore raw

On Mittwoch, 18. April 2018 16:56:23 CEST Kalle Valo wrote:
[...]

Quoted 4 lines

I added these now, please check that I did it correctly. It's very easy for me to make a mistake.

https://github.com/kvalo/ath10k-firmware/commit/66be3a48d9cf17ace8413cf478a5954483393af4

Thanks, this looks exactly like requested. The change looks good and I will prepare the OpenWrt change.

pending
=======

* Asus RT-AC58U

- submitted before the guide was published
- http://lists.infradead.org/pipermail/ath10k/2017-March/009454.html

* Netgear EX6100v2/EX6150v2

- http://lists.infradead.org/pipermail/ath10k/2018-February/010845.html

* 8devices Jalapeno

- http://lists.infradead.org/pipermail/ath10k/2018-March/010916.html

* Compex WLE1216V5-20 + Compex ?

- http://lists.infradead.org/pipermail/ath10k/2018-March/010998.html

* GL.iNet GL-B1300

- http://lists.infradead.org/pipermail/ath10k/2018-March/011058.html

* OpenMesh A62

- http://lists.infradead.org/pipermail/ath10k/2018-March/011081.html

* AVM FRITZ!Box 4040

- http://lists.infradead.org/pipermail/ath10k/2018-April/011178.html

accepted
========

* OpenMesh A42

- http://lists.infradead.org/pipermail/ath10k/2017-November/010470.html
- http://lists.infradead.org/pipermail/ath10k/2017-December/010543.html
- https://github.com/kvalo/ath10k-firmware/commit/5cd2bacd8e22217335e539b416d0cb8d59f8e312

* Meraki MR33
- http://lists.infradead.org/pipermail/ath10k/2018-April/011179.html
- https://github.com/kvalo/ath10k-firmware/commit/66be3a48d9cf17ace8413cf478a5954483393af4

Kind regards,
Sven

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k