aspriel@xxxxxxxxx writes: > The bcm43xx family of wifi chipsets found its way to different > groups inside and outside Broadcom. For the fullmac devices this > means that in those difference groups firmware is being developed > and the firmware api is bound to diverge. This series introduces > a design change to accomodate supporting multiple firmware api's. > The vender-specific support can be compiled in brcmfmac or > built as a separate module. Currently the vendor-specific support > does not have any real effect. At the momemt looking into SAE support > which appear to be different for Cypress devices so that might be a > first use-case. Meanwhile wanted to put this series out there and > get feedback on it. Some ideas were taken from iwlwifi which does > similar things for iwlmvm, iwldvm, etc. > > The patches apply to the main branch of the wireless-next repository. > > Arend van Spriel (7): > brcmfmac: add function to unbind device to bus layer api > brcmfmac: add firmware vendor info in driver data > brcmfmac: add support for vendor-specific firmware api > brcmfmac: add support for Cypress firmware api > brcmfmac: add support Broadcom BCA firmware api > brcmfmac: add vendor name in revinfo debugfs file > brcmfmac: introduce BRCMFMAC exported symbols namespace I think there's something wrong in mail formatting, tried to apply just for a test and it failed: error: git diff header lacks filename information when removing 1 leading pathname component (line 7) error: could not build fake ancestor hint: Use 'git am --show-current-patch=diff' to see the failed patch Applying: brcmfmac: add function to unbind device to bus layer api Patch failed at 0001 brcmfmac: add function to unbind device to bus layer api -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
