Re: [PATCH] brcmfmac: update STA info struct to the v5
From: Rafał Miłecki <rafal@milecki.pl>
Date: 2018-07-01 10:47:44
On 2018-06-30 20:48, Arend van Spriel wrote:
On 6/28/2018 12:36 PM, Rafał Miłecki wrote:quoted
From: Rafał Miłecki <rafal@milecki.pl> That struct is used when querying firmware for the STA. It seem is has been changing during the time. Luckily its format seems to be backward compatible starting with v2 (the only breakage was v1 -> v2). The version that was supported by brcmfmac so far was v4. It was what 43602a1 and 4366b1 firmwares (7.35.177.56 and 10.10.69.3309 accordingly) were using. It also seems to be used by early 4366c0 firmwares (10.10.69.6908 and 10.10.69.69017). The problem appears when switching to the 10.10.122.20 firmware. It uses v5 and instead of falling back to v4 when submitted buffer isn't big enough it fallbacks to the v3. To receive all v4 specific info with the newest firmware we have to submit a struct (buffer) that matches v5.So do you have firmware that actually return v5 in the 'ver' field. I am asking because I see a comment that version 5 is obsoleted and in recent branch we are at version 7. Just curious what the actual version is. If you do not explicitly need version 5 I would prefer to skip it and move to version 6 struct. Otherwise it is...
Yes. As stated in the commit message, firmware 10.10.122.20 uses v5. I didn't list vendors using that firmware, but if you take a look at the side thread "Research + questions on brcmfmac and support for monitor mode", you'll see that 10.10.122.20 is used in: 1) FW_EA9500v2_EA9500S_2.1.1.183171_prod.img 2) GT-AC5300_3.0.0.4_382_15984-gf481f58_cferom_ubi_0824.w 3) ArcherC5400X(US)_171023.bin That means I explicitly need v5 to make brcmfmac work with any 10.10.122.20 firmware from above images. Unfortunately I didn't find any vendor release their GPL package with Broadcom's SDK using v6 or v7. I hope it's backward compatible and maybe you'll be able to provide patch on top of mine?
Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>
Thanks!