On 14/03/2024 15:33, Jeff Johnson wrote: > On 3/7/2024 8:46 AM, Jeff Johnson wrote: > >> On 3/7/2024 7:29 AM, Marc Gonzalez wrote: >> >>> Have you heard back from the dev team? >>> >>> Do they confirm that an issue involving missing MSA_READY notifications >>> was ever noticed? >>> >>> What devices were affected? (All msm8998? A subset of msm8998?) >>> >>> Was the issue eventually fixed? >>> (Probably fixed, otherwise newer devices would be affected) >> >> The feedback I received was "it might be ok to change all ath10k qmi to >> skip waiting for msa_ready", and it was pointed out that ath11k (and >> ath12k) do not wait for it. >> >> However with so many deployed devices, "might be ok" isn't a strong >> argument for changing the default behavior. >> >> So my preference would be to use the firmware capability in the board >> file that Kalle has recommended. > > Marc, > I finally have an engineer who wants to research this further. > Can you provide the kernel log that shows the firmware version being used? Hello Jeff, Is this the line you're after: [ 32.367011] ath10k_snoc 18800000.wifi: qmi fw_version 0x100204b2 fw_build_timestamp 2019-09-04 03:01 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HL.1.0-01202-QCAHLSWMTPLZ-1.221523.2 Hopefully, my Debian setup will soon be 100% functional so I can easily tweak the kernel, and add more logs. Bonus question: Is it legal for my company to publish our versions of qcom firmwares on linux-firmware? (Perhaps a generic set of FWs would work; but AFAIU, there is some kind of signature verification at some point) Regards
