* ath10k-firmware: QCA4019 hw1.0: Add Meraki MR33 specific BDFs
@ 2018-04-17 8:15 Sven Eckelmann
2018-04-17 15:04 ` Chris Blake
2018-04-18 16:56 ` Kalle Valo
0 siblings, 2 replies; 4+ messages in thread
From: Sven Eckelmann @ 2018-04-17 8:15 UTC (permalink / raw)
To: ath10k; +Cc: Chris Blake, Kalle Valo
[-- 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
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: ath10k-firmware: QCA4019 hw1.0: Add Meraki MR33 specific BDFs
2018-04-17 8:15 ath10k-firmware: QCA4019 hw1.0: Add Meraki MR33 specific BDFs Sven Eckelmann
@ 2018-04-17 15:04 ` Chris Blake
2018-04-18 16:56 ` Kalle Valo
1 sibling, 0 replies; 4+ messages in thread
From: Chris Blake @ 2018-04-17 15:04 UTC (permalink / raw)
To: Sven Eckelmann; +Cc: Kalle Valo, ath10k, Christian Lamparter
On Tue, Apr 17, 2018 at 3:15 AM, Sven Eckelmann
<sven.eckelmann@openmesh.com> wrote:
> 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
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
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ath10k-firmware: QCA4019 hw1.0: Add Meraki MR33 specific BDFs
2018-04-17 8:15 ath10k-firmware: QCA4019 hw1.0: Add Meraki MR33 specific BDFs Sven Eckelmann
2018-04-17 15:04 ` Chris Blake
@ 2018-04-18 16:56 ` Kalle Valo
2018-04-19 6:40 ` Sven Eckelmann
1 sibling, 1 reply; 4+ messages in thread
From: Kalle Valo @ 2018-04-18 16:56 UTC (permalink / raw)
To: Sven Eckelmann; +Cc: Chris Blake, ath10k@lists.infradead.org
Sven Eckelmann <sven.eckelmann@openmesh.com> writes:
> 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")
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
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-04-19 6:40 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-04-17 8:15 ath10k-firmware: QCA4019 hw1.0: Add Meraki MR33 specific BDFs Sven Eckelmann
2018-04-17 15:04 ` Chris Blake
2018-04-18 16:56 ` Kalle Valo
2018-04-19 6:40 ` Sven Eckelmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox