Broadcom bcm4360 linux driver
![broadcom bcm4360 linux driver broadcom bcm4360 linux driver](https://i.stack.imgur.com/IsiuP.jpg)
In-Hardware MAC address filter (b43 only impossible on b43legacy hardware).In-Hardware traffic de/encryption (relieves your CPU)."Monitor while operating" and multiple monitor interfaces.IRC: server is, channel is #bcm-users (English please).Please note that we do not support wl or brcm80211 drivers. Often the PCI-ID equals the Chip ID, but that is not always the case and it is a constant source of confusion.įor a list of available devices, please see the device list. Note that the PCI-ID is not in direct correlation with the Chip ID. Find that phrase in the below table to determine support. Ignore everything, except the last part inside of the. The command will output a string similar to this example:Ġ001:01:01.0 Network controller : Broadcom Corporation BCM4318 802.11g Wireless LAN Controller (rev 02) To find out whether a PCI device is supported by the b43 or b43legacy drivers, issue this lspci command: G-PHY devices: not working with kernels 3.15 and 3.16-rc1 (a regression). A workaround for older kernel is to use PIO mode (b43.pio=1 module param). BCM4321: some cards do not work in DMA mode with kernel 3.1 and older.Using PIO (module param) can be used as workaround for 2.6.īCM4318 chipset: AP mode does not work because of packet loss in high transmission rates. LP-PHY devices: DMA errors on some machines with kernel 2.6.
BROADCOM BCM4360 LINUX DRIVER DRIVERS
See Switching between drivers for howto on choosing driver. It is possible to use only one driver at a moment, they are conflicting each other. The b43/b43legacy driver is not meant to support such a device. See rndis_wlan for 14e4:4320 and brcmfmac for others. If you have a Broadcom USB device, it's most likely a FullMAC device. The b43/b43legacy drivers require proprietary firmware to be loaded onto the wireless chip before it can operate, see below.