| Message ID | 20221129135446.151065-1-arend.vanspriel@broadcom.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | brcmfmac: support devices from multiple vendors | expand |
On 11/29/2022 2:54 PM, Arend van Spriel wrote: > Took my sweet time coming with this follow-up series, but here > it is. Hopefully, sending patches is working for me now. > > 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. > > The patches apply to the main branch of the wireless-next repository. Just realized I forgot the 'wifi:' prefix. Hopefully you can forgive me this time? If not, I can resend. Regards, Arend
Arend van Spriel <arend.vanspriel@broadcom.com> writes: > On 11/29/2022 2:54 PM, Arend van Spriel wrote: >> Took my sweet time coming with this follow-up series, but here >> it is. Hopefully, sending patches is working for me now. >> >> 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. >> >> The patches apply to the main branch of the wireless-next repository. > > Just realized I forgot the 'wifi:' prefix. Hopefully you can forgive > me this time? If not, I can resend. Yeah, I can add that. When we switched to using "wifi:" I was mentally (and in my tools) prepared to adding those the next couple of years :)
On 12/1/2022 12:12 PM, Kalle Valo wrote: > Arend van Spriel <arend.vanspriel@broadcom.com> writes: > >> On 11/29/2022 2:54 PM, Arend van Spriel wrote: >>> Took my sweet time coming with this follow-up series, but here >>> it is. Hopefully, sending patches is working for me now. >>> >>> 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. >>> >>> The patches apply to the main branch of the wireless-next repository. >> >> Just realized I forgot the 'wifi:' prefix. Hopefully you can forgive >> me this time? If not, I can resend. > > Yeah, I can add that. When we switched to using "wifi:" I was mentally > (and in my tools) prepared to adding those the next couple of years :) From my side I will try to shorten that period ;-D Gr. AvS