User Tools

Site Tools


en:users:drivers:brcm80211

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
en:users:drivers:brcm80211 [2020/06/11 01:02]
Matteo Scordino [Firmware installation]
en:users:drivers:brcm80211 [2024/02/12 20:17]
Arend van Spriel [fullmac driver specifics]
Line 119: Line 119:
  
 For the USB driver no nvram file is //​strictly//​ needed: in fact, the driver only loads the firmware blob and does not look for an nvram text file. However, the nvram parameters are still required and they are already part of the firmware blob. This is a TRX file which contains the nvram parameters as a sequence of zero-terminated plain text strings, appended at the end of the last section. For the USB driver no nvram file is //​strictly//​ needed: in fact, the driver only loads the firmware blob and does not look for an nvram text file. However, the nvram parameters are still required and they are already part of the firmware blob. This is a TRX file which contains the nvram parameters as a sequence of zero-terminated plain text strings, appended at the end of the last section.
-For an example of how to modify/add nvram parameters for USB devices, see [[https://​blog.elimo.io/​2020/​06/​05/​pta-coexistence.html|this post]]+For an example of how to modify/add nvram parameters for USB devices, see [[https://​blog.elimo.io/​2020/​06/​05/​pta-coexistence/|this post]]
  
 The firmware files are located in the linux-firmware repository and can be copied as is to /​lib/​firmware/​brcm. ​ The firmware files are located in the linux-firmware repository and can be copied as is to /​lib/​firmware/​brcm. ​
Line 150: Line 150:
 For driver issues and/or bug reports, please use one or both: For driver issues and/or bug reports, please use one or both:
  
-[[mailto:​brcm80211-dev-list.pdl@broadcom.com|brcm80211-dev-list.pdl@broadcom.com]]\\ +[[mailto:​brcm80211@lists.linux.dev|brcm80211@lists.linux.dev]]\\ 
-[[mailto:brcm80211-dev-list@cypress.com|brcm80211-dev-list@cypress.com]]+[[mailto:linux-wireless@vger.kernel.org|linux-wireless@vger.kernel.org]]\\
  
 For any other questions feel free to contact the developers listed below: ​ For any other questions feel free to contact the developers listed below: ​
  
 Arend van Spriel ​       [[mailto:​arend.vanspriel@broadcom.com|arend.vanspriel@broadcom.com]]\\ Arend van Spriel ​       [[mailto:​arend.vanspriel@broadcom.com|arend.vanspriel@broadcom.com]]\\
-Franky Lin              [[mailto:​franky.lin@broadcom.com|franky.lin@broadcom.com]]\\ 
-Hante Meuleman ​         [[mailto:​hante.meuleman@broadcom.com|hante.meuleman@broadcom.com]]\\ 
-Chi-Hsien Lin           ​[[mailto:​Chi-Hsien.Lin@cypress.com|Chi-Hsien.Lin@cypress.com]]\\ 
-Wright Feng             ​[[mailto:​Wright.Feng@cypress.com|Wright.Feng@cypress.com]] 
  
 ===== Developer information ===== ===== Developer information =====
Line 176: Line 172:
             * monitor mode              * monitor mode 
 ==== fullmac driver specifics ==== ==== fullmac driver specifics ====
-              * Integrated with cfg80211  +The brcmfmac driver ​is based on the DHD driver, which is also released in AOSP under the name bcmdhd. Although similar the brcmfmac driver has been reworked significantly. In the figure below the layering of the brcmfmac is shown. It was made couple of years ago so it may not be accurate. 
-              * Most of Mac functionality ​is performed ​on chip  +{{:​en:​users:​drivers:​brcm80211:​brcmfmac-layering.png?​500|}} 
-              * support for SDIO, USB and PCIe  +The bus layer supports ​SDIO, USBand PCIe. The protocol layer support msgbuf protocol used for PCIe devices and BCDC which is used for SDIO and USB devices.
-              * SoftAP  +
-              * P2P  +
-              * TDLS +
 ==== Get the code ==== ==== Get the code ====
  
en/users/drivers/brcm80211.txt · Last modified: 2024/03/20 10:46 by Peter Robinson