"Youghandhar Chintala (Temp)" writes:
> On 11/1/2022 2:31 PM, Kalle Valo wrote:
>
>> BTW Youghandhar, your quotes were broken in this mail so your reply was
>> difficult to find. See here:
>>
>>
On 11/1/2022 2:31 PM, Kalle Valo wrote:
(fixing quotation)
"Youghandhar Chintala (Temp)" writes:
On 10/28/2022 12:19 AM, Jeff Johnson wrote:
On 10/26/2022 3:22 AM, Youghandhar Chintala wrote:
+static void ath10k_qmi_add_wlan_ver_smem(struct ath10k *ar, char
*fw_build_id)
const char
(fixing quotation)
"Youghandhar Chintala (Temp)" writes:
> On 10/28/2022 12:19 AM, Jeff Johnson wrote:
>
>> On 10/26/2022 3:22 AM, Youghandhar Chintala wrote:
>>> +static void ath10k_qmi_add_wlan_ver_smem(struct ath10k *ar, char
>>> *fw_build_id)
>>
>> const char *fw_build_id?
>>
>>> +{
>>>
On 10/26/2022 3:22 AM, Youghandhar Chintala wrote:
In a SoC based solution, it would be useful to know the versions of the
various binary firmware blobs the system is running on. On a QCOM based
SoC, this info can be obtained from socinfo debugfs infrastructure. For
this to work, respective
://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git ath-next
patch link:
https://lore.kernel.org/r/20221026102257.19919-1-quic_youghand%40quicinc.com
patch subject: [PATCH] wifi: ath10k: Add WLAN firmware image version info into
smem
config: ia64-allyesconfig (attached as .config)
compiler
In a SoC based solution, it would be useful to know the versions of the
various binary firmware blobs the system is running on. On a QCOM based
SoC, this info can be obtained from socinfo debugfs infrastructure. For
this to work, respective subsystem drivers have to export the firmware
version
