> Ah, my good friend qcacld-2.0.
>
> I'd expect to see something written to kmsg, but not sure it is there for USB.
>
> for QMI there is:
> ath10k_info(ar, "qmi fw_version 0x%x fw_build_timestamp %s
> fw_build_id %s",
> qmi->fw_version, qmi->fw_build_timesta
On 9/4/2024 11:28 AM, Tomas Paukrt wrote:
>> Also the Tested-on tag should include the firmware version information as
>> well.
>
> Hi Jeff,
>
> I tested it with manually converted firmware from
> https://github.com/8devices/qcacld-2.0/tree/CNSS.LEA.NRT_3.0/firmware_bin/usb
> which does not in
> Also the Tested-on tag should include the firmware version information as
> well.
Hi Jeff,
I tested it with manually converted firmware from
https://github.com/8devices/qcacld-2.0/tree/CNSS.LEA.NRT_3.0/firmware_bin/usb
which does not include any explicit version.
What version should I write
On 8/30/2024 4:28 AM, Tomas Paukrt wrote:
> Add USB device ID for modules based on Atheros QCA9377-7 chipset like
> 8devices BLUE bean or SparkLAN WUBQ-159ACN.
>
> Tested-on: QCA9377 hw1.1 USB
Since Tested-on is not an official upstream tag there should be a blank line
between it and the official
Add USB device ID for modules based on Atheros QCA9377-7 chipset like
8devices BLUE bean or SparkLAN WUBQ-159ACN.
Tested-on: QCA9377 hw1.1 USB
Signed-off-by: Tomas Paukrt
---
drivers/net/wireless/ath/ath10k/usb.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wireless/ath/ath10k
