ath10k-firmware: QCA4019 hw1.0: Add FRITZ!Box 4040 specific BDFs

ath10k-firmware: QCA4019 hw1.0: Add FRITZ!Box 4040 specific BDFs

[Sven Eckelmann]

[-- Attachment #1.1.1: Type: text/plain, Size: 1483 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 QCA401x based board (most likely on qcom-ipq4019-ap.dk01.1)
  - 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)

  - Christian 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=16,variant=AVM-FRITZBox-4040
      sha256sum:
      eb866d036149fe4ba35f3f9d0d97e51969b1f1dbac6ea962daf9012ffa75427a
    + bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=AVM-FRITZBox-4040
      sha256sum:
      f3dc3c2f10037722006e9e7e5173a7468649e9a554f564323f9580f4a8bba10a

* 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=16,variant=AVM-FRITZBox-4040.bin --]
[-- Type: application/octet-stream, Size: 12064 bytes --]

[-- Attachment #1.1.3: bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=AVM-FRITZBox-4040.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

Re: ath10k-firmware: QCA4019 hw1.0: Add FRITZ!Box 4040 specific BDFs

[Christian Lamparter]

On Tuesday, 17. April 2018 10:15:42 CEST Sven Eckelmann wrote:
> 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 QCA401x based board (most likely on qcom-ipq4019-ap.dk01.1)
>   - 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)
> 
>   - Christian didn't include this info in the OpenWrt commit (maybe he can add
>     it here)
>   - most likely taken from stock firmware image
Yes, the files are coming from the stock firmware image. The firmware image:
FRITZ.Box_4040.en-de-es-it-fr-pl.155.06.83.image can be found here [0].

In order to extract board data files:
 0. Download FRITZ.Box_4040.en-de-es-it-fr-pl.155.06.83.image
 1. tar xf FRITZ.Box_4040.en-de-es-it-fr-pl.155.06.83.image
 2. binwalk -e ./var/tmp/kernel.image

The boarddata_0.bin and boarddata_1.bin are located in:
 ./_kernel.image.extracted/squashfs-root/lib/firmware/IPQ4019/hw.1

eb866d036149fe4ba35f3f9d0d97e51969b1f1dbac6ea962daf9012ffa75427a  boarddata_0.bin
f3dc3c2f10037722006e9e7e5173a7468649e9a554f564323f9580f4a8bba10a  boarddata_1.bin

The boarddata_0.bin file matches the
"bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=AVM-FRITZBox-4040" 
file Sven attached (see checksums down below). And the boarddata_1.bin 
file matches the 
"bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=AVM-FRITZBox-4040" file
 
> * 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=16,variant=AVM-FRITZBox-4040
>       sha256sum:
>       eb866d036149fe4ba35f3f9d0d97e51969b1f1dbac6ea962daf9012ffa75427a
>     + bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=AVM-FRITZBox-4040
>       sha256sum:
>       f3dc3c2f10037722006e9e7e5173a7468649e9a554f564323f9580f4a8bba10a
> 
> * 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

[0] <http://ftp.avm.de/fritzbox/fritzbox-4040/deutschland/fritz.os/FRITZ.Box_4040.en-de-es-it-fr-pl.155.06.83.image>



_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: ath10k-firmware: QCA4019 hw1.0: Add FRITZ!Box 4040 specific BDFs

[Sven Eckelmann]

[-- Attachment #1.1: Type: text/plain, Size: 2191 bytes --]

On Dienstag, 17. April 2018 10:15:42 CEST Sven Eckelmann wrote:
[...]
>   - QCA4019 hw1.0
> 
>     + bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=AVM-FRITZBox-4040
>       sha256sum:
>       eb866d036149fe4ba35f3f9d0d97e51969b1f1dbac6ea962daf9012ffa75427a
>     + bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=AVM-FRITZBox-4040
>       sha256sum:
>       f3dc3c2f10037722006e9e7e5173a7468649e9a554f564323f9580f4a8bba10a

Thanks,

looks like the boardata files were added in
https://github.com/kvalo/ath10k-firmware/commit/81a745e6a529565438ee4aea357a8a59e9564848

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

* 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
  - QCA4019 files added in 
    https://github.com/kvalo/ath10k-firmware/commit/a262aac7cfe5ae5833378b4f1b0634f873a4df4d
  - "bus=pci,bmi-chip-id=0,bmi-board-id=16,variant=OM-A62" must still 
    be moved to QCA9888 hw 2.0 board-2.bin


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

* Compex WLE1216V5-20 + Compex ?

  - http://lists.infradead.org/pipermail/ath10k/2018-March/010998.html
  - https://github.com/kvalo/ath10k-firmware/commit/b1dd338046a385743c483a47e8eef276adaba0c0

* AVM FRITZ!Box 4040

  - http://lists.infradead.org/pipermail/ath10k/2018-April/011178.html
  - https://github.com/kvalo/ath10k-firmware/commit/81a745e6a529565438ee4aea357a8a59e9564848

Kind regards,
	Sven

[-- 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

Re: ath10k-firmware: QCA4019 hw1.0: Add FRITZ!Box 4040 specific BDFs

[Kalle Valo]

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 QCA401x based board (most likely on qcom-ipq4019-ap.dk01.1)
>   - 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)
>
>   - Christian 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=16,variant=AVM-FRITZBox-4040
>       sha256sum:
>       eb866d036149fe4ba35f3f9d0d97e51969b1f1dbac6ea962daf9012ffa75427a
>     + bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=AVM-FRITZBox-4040
>       sha256sum:
>       f3dc3c2f10037722006e9e7e5173a7468649e9a554f564323f9580f4a8bba10a
>
> * 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")

Added, please check the results:

https://github.com/kvalo/ath10k-firmware/commit/81a745e6a529565438ee4aea357a8a59e9564848

New:
bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=AVM-FRITZBox-4040

Changed:


Deleted:

1 board image(s) added, 0 changed, 0 deleted, 17 in total



New:
bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=AVM-FRITZBox-4040

Changed:


Deleted:

1 board image(s) added, 0 changed, 0 deleted, 18 in total

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k