This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
en:users:drivers:brcm80211 [2020/06/10 15:41] Matteo Scordino [Firmware installation] |
en:users:drivers:brcm80211 [2020/06/10 18:10] Matteo Scordino [Firmware installation] |
||
---|---|---|---|
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://www.linkedin.com/feed/update/urn:li:activity:6675830103454339072/|this article]] | + | For an example of how to modify/add nvram parameters for USB devices, see [[https://blog.elimo.io/reverse-engineering/wifi/mesh/thread/802.15.4/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. |