From: Kalle Valo <kvalo@kernel.org>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: [V2] ath10k-firmware: QCA9888 hw2.0: Add BDF for Linksys EA8300 [2/2]
Date: Fri, 17 Mar 2023 13:49:21 +0200 [thread overview]
Message-ID: <871qlnk37i.fsf@kernel.org> (raw)
In-Reply-To: <35f7ccc8-9669-966a-516c-d7754d243d02@gmail.com> (Christian Lamparter's message of "Fri, 1 Jul 2022 13:25:15 +0200")
Christian Lamparter <chunkeey@gmail.com> writes:
> From: Jeff Kletsky <lede@allycomm.com>
>
> This is a IPQ4019-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.
>
> Two similar messages will be sent, one for each chipset, as per the directions.
>
>
> The files selected and their original names and organization include:
>
> 27d9dfe1e86c3befe808f89dd3cd105b OEM/QCA9888/IC/boardData_2_0_QCA9888_5G_Y9690_SBS_HB.bin
> 7f2f0de6c0fb2df1d642895d8233d3ef OEM/QCA9888/EU/boardData_2_0_QCA9888_5G_Y9690_SBS_HB.bin
> 62049f88a498e51870973143e376e7af OEM/QCA9888/FCC/boardData_2_0_QCA9888_5G_Y9690_SBS_HB.bin
> 27d71485fc4987bc1c11b7744c373b59 OEM/QCA9888/AH/boardData_2_0_QCA9888_5G_Y9690_SBS_HB.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/QCA9888/${JD}/boardData_2_0_QCA9888_5G_Y9690_SBS_HB.bin \
> ${dest}/bus=pci,bmi-chip-id=0,bmi-board-id=23,variant=linksys-ea8300-${jd}
> done
>
>
> Renamed board files are individually attached to QCA9888 messages.
>
> - QCA9888 hw 2.0:
>
> bus=pci,bmi-chip-id=0,bmi-board-id=23,variant=linksys-ea8300-eu
> md5sum: 7f2f0de6c0fb2df1d642895d8233d3ef
>
> bus=pci,bmi-chip-id=0,bmi-board-id=23,variant=linksys-ea8300-ic
> md5sum: 27d9dfe1e86c3befe808f89dd3cd105b
>
> bus=pci,bmi-chip-id=0,bmi-board-id=23,variant=linksys-ea8300-ah
> md5sum: 27d71485fc4987bc1c11b7744c373b59
>
> bus=pci,bmi-chip-id=0,bmi-board-id=23,variant=linksys-ea8300-fcc
> md5sum: 62049f88a498e51870973143e376e7af
Thanks, added to QCA9888/hw2.0/board-2.bin:
New:
bus=pci,bmi-chip-id=0,bmi-board-id=23,variant=linksys-ea8300-ah
bus=pci,bmi-chip-id=0,bmi-board-id=23,variant=linksys-ea8300-eu
bus=pci,bmi-chip-id=0,bmi-board-id=23,variant=linksys-ea8300-fcc
bus=pci,bmi-chip-id=0,bmi-board-id=23,variant=linksys-ea8300-ic
Changed:
Deleted:
4 board image(s) added, 0 changed, 0 deleted, 16 in total
https://github.com/kvalo/ath10k-firmware/commit/82f428f4bb780b3462656be8e05ba7bd8052c658
--
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:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 11:25 [V2] ath10k-firmware: QCA9888 hw2.0: Add BDF for Linksys EA8300 [2/2] Christian Lamparter
2023-03-17 11:49 ` 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=871qlnk37i.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