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: bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=Meraki-MR33.bin
Description: Binary data

Attachment: bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=Meraki-MR33.bin
Description: Binary data

Attachment: signature.asc
Description: This is a digitally signed message part.

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

Reply via email to