From: Kalle Valo <kvalo@kernel.org>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: [V2] ath10k-firmware: QCA4019 hw1.0: Add BDF for Linksys EA8300 [1/2]
Date: Fri, 17 Mar 2023 13:35:10 +0200 [thread overview]
Message-ID: <87jzzflifl.fsf@kernel.org> (raw)
In-Reply-To: <4ac52436-699f-cd31-4538-a63ba37505df@gmail.com> (Christian Lamparter's message of "Fri, 1 Jul 2022 13:25:13 +0200")
Christian Lamparter <chunkeey@gmail.com> writes:
> From: Jeff Kletsky <lede@allycomm.com>
>
> This is a QCA4019-based device with a PCI-attached QCA9888
> supplying a third radio on 5 GHz. The OEM's firmware and source
> suggest that this device is "based on Qualcomm AP DK07.1-c1"
>
> Linksys ships four market-specific variants of this device, notated as
> -AH, -EU, (no suffix), and -CA. They supply four sets of pre-cal board
> files in their firmware, AH, EU, FCC, and IC. The corresponding files
> differ from each other, and appear to provide different parameters in
> the different regions. The OEM firmware copies the appropriate set of
> files into place based on examining the SKU of the device at boot.
>
> These board files may be obtained from extraction of the OEM firmware
> Ver. 1.1.4.191539, Latest Date: 11/8/2018, 49.0 MB
> http://downloads.linksys.com/downloads/firmware/FW_EA8300_1.1.4.191539_prod.img
> Ver. 1.1.3.184925, Latest Date: 11/15/2017, 47.4 MB
> http://downloads.linksys.com/downloads/firmware/FW_EA8300_1.1.3.184925_prod.img
> and/or from a running device. There does not appear to be a difference
> in the board files between the two firmware versions.
>
> DTS for the EA8300 under OpenWrt expects that the variant be encoded
> as, for example, linksys-ea8300-fcc, with the lower-cased suffix
> indicating the OEM's regional code, or -fcc.
>
>
> The files selected and their original names and organization include:
>
> 435d236890521515feffc834218ca594 OEM/IPQ4019/IC/boardData_1_0_IPQ4019_DK04_5G.bin
> e8858ab9259f7d4372040da1c592d1cc OEM/IPQ4019/IC/boardData_1_0_IPQ4019_DK04_2G.bin
> d6d7ed00db985b4d8c48ccc3fe10fa87 OEM/IPQ4019/EU/boardData_1_0_IPQ4019_DK04_5G.bin
> 5cef8208a0345c1469494e44e1f370f1 OEM/IPQ4019/EU/boardData_1_0_IPQ4019_DK04_2G.bin
> 0e820f5946b5773ad9f4a74809c05b79 OEM/IPQ4019/FCC/boardData_1_0_IPQ4019_DK04_5G.bin
> 057ed5528e360197c2239796710cb61c OEM/IPQ4019/FCC/boardData_1_0_IPQ4019_DK04_2G.bin
> 0171919a4576199ae88e8831f72c03fe OEM/IPQ4019/AH/boardData_1_0_IPQ4019_DK04_5G.bin
> a8e23769dc98da97b6c70a4f601ffca8 OEM/IPQ4019/AH/boardData_1_0_IPQ4019_DK04_2G.bin
>
>
> The files were renamed as follows:
>
> for JD in AH EU FCC IC ; do
> jd=$(echo "$JD" | tr 'A-Z' 'a-z')
> cp -vp OEM/IPQ4019/${JD}/boardData_1_0_IPQ4019_DK04_2G.bin \
> ${dest}/bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=linksys-ea8300-${jd}
> cp -vp OEM/IPQ4019/${JD}/boardData_1_0_IPQ4019_DK04_5G.bin \
> ${dest}/bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=linksys-ea8300-${jd}
> done
>
>
> Renamed board files are individually attached to the IPQ4019
> messages. dmesg excerpts are from the device running OpenWrt with
> locally crafted, aggregate board files.
>
>
> - QCA4019 hw1.0
> bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=linksys-ea8300-ah
> md5sum: a8e23769dc98da97b6c70a4f601ffca8
>
> bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=linksys-ea8300-fcc
> md5sum: 057ed5528e360197c2239796710cb61c
>
> bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=linksys-ea8300-eu
> md5sum: 5cef8208a0345c1469494e44e1f370f1
>
> bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=linksys-ea8300-ic
> md5sum: e8858ab9259f7d4372040da1c592d1cc
>
>
> bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=linksys-ea8300-eu
> md5sum: d6d7ed00db985b4d8c48ccc3fe10fa87
>
> bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=linksys-ea8300-ic
> md5sum: 435d236890521515feffc834218ca594
>
> bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=linksys-ea8300-fcc
> md5sum: 0e820f5946b5773ad9f4a74809c05b79
>
> bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=linksys-ea8300-ah
> md5sum: 0171919a4576199ae88e8831f72c03fe
Thanks, added to QCA4019/hw1.0/board-2.bin:
New:
bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=linksys-ea8300-ah
bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=linksys-ea8300-eu
bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=linksys-ea8300-fcc
bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=linksys-ea8300-ic
bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=linksys-ea8300-ah
bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=linksys-ea8300-eu
bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=linksys-ea8300-fcc
bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=linksys-ea8300-ic
Changed:
Deleted:
8 board image(s) added, 0 changed, 0 deleted, 114 in total
https://github.com/kvalo/ath10k-firmware/commit/0c3378faf4622bea1d328e6e004f3972777f5ac2
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2023-03-17 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 11:25 [V2] ath10k-firmware: QCA4019 hw1.0: Add BDF for Linksys EA8300 [1/2] Christian Lamparter
2023-03-17 11:35 ` Kalle Valo [this message]
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=87jzzflifl.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=chunkeey@gmail.com \
/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