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
en:users:drivers:brcm80211 [2016/06/09 14:35]
Ben Gamari [Firmware installation]
en:users:drivers:brcm80211 [2020/06/11 01:02] (current)
Matteo Scordino [Firmware installation]
Line 116: Line 116:
 === Current === === Current ===
  
-For SDIO driver you need to copy the nvram for your system and place it in /​lib/​firmware/​brcm. The nvram file name depends on the chip you have. The kernel log will tell you the exact file name. For the USB driver no nvram file is needed. ​+For SDIO driver you need to copy the nvram for your system and place it in /​lib/​firmware/​brcm. The nvram file name depends on the chip you have. The kernel log will tell you the exact file name.  
 + 
 +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]]
  
 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 133: Line 136:
  
 === NVRAM from EFI === === NVRAM from EFI ===
-Some new non-PCIe ​devices are storing the nvram which is needed in addition to the firmware by the driver in an EFI variable and the Windows driver can access it. Currently brcmfmac does not support this automatically.+Some new devices are storing the nvram which is needed in addition to the firmware by the driver in an EFI variable and the Windows driver can access it (this file should be optional in the case of PCIe devices). Currently brcmfmac does not support this automatically.
 First mount the efi vars into sysfs: First mount the efi vars into sysfs:
   mount -t efivarfs none /​sys/​firmware/​efi/​efivars   mount -t efivarfs none /​sys/​firmware/​efi/​efivars
Line 145: Line 148:
 ===== Contact Info ===== ===== Contact Info =====
  
-For driver issues and/or bug reports, please use: +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-dev-list.pdl@broadcom.com|brcm80211-dev-list.pdl@broadcom.com]]\\ 
 +[[mailto:​brcm80211-dev-list@cypress.com|brcm80211-dev-list@cypress.com]]
  
 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]]\\ 
-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]]\\ 
-Hante Meuleman ​         [[mailto:​hante.meuleman@broadcom.com|hante.meuleman@broadcom.com]]  +Wright Feng             ​[[mailto:​Wright.Feng@cypress.com|Wright.Feng@cypress.com]]
- +
-Brett Rudley ​           ​[[mailto:brett.rudley@broadcom.com|brett.rudley@broadcom.com]]  +
  
 ===== Developer information ===== ===== Developer information =====
Line 226: Line 227:
 ==== Regulatory Implementation for brcmsmac ==== ==== Regulatory Implementation for brcmsmac ====
  
-This generation of chips contain additional ​ regulatory support independent of the driver. The devices use a single ​ worldwide regulatory domain, with channels ​12-14 (2.4 GHz band) and  channels 52-64 and 100-140 (5 GHz band) restricted to passive operation. ​ Transmission on those channels is suppressed until appropriate other  traffic is observed on those channels. Within the driver, we use the  ficticious country code "​X2"​ to represent this worldwide regulatory ​ domain. There is currently no interface to configure a different domain. ​ The driver reads the SROM country code from the chip and hands it up to  mac80211 as the regulatory hint, however this information is otherwise ​ unused with the driver. ​+This generation of chips contain additional ​ regulatory support independent of the driver. The devices use a single ​ worldwide regulatory domain, with channels ​1-11 (2.4 GHz band) and  channels 52-64 and 100-140 (5 GHz band) restricted to passive operation. ​ Transmission on those channels is suppressed until appropriate other  traffic is observed on those channels. Within the driver, we use the  ficticious country code "​X2"​ to represent this worldwide regulatory ​ domain. There is currently no interface to configure a different domain. ​ The driver reads the SROM country code from the chip and hands it up to  mac80211 as the regulatory hint, however this information is otherwise ​ unused with the driver. ​
  
en/users/drivers/brcm80211.1465482942.txt.gz · Last modified: 2016/06/09 14:35 by Ben Gamari