On 6 February 2016 at 00:53, Samuel Sieb <samuel@xxxxxxxx> wrote: > However, what happens is: > Feb 04 11:55:50 localhost kernel: bcma: bus0: Found chip with id 43142, rev > 0x01 and package 0x08 > Feb 04 11:55:50 localhost kernel: bcma: bus0: Core 0 found: ChipCommon > (manuf 0x4BF, id 0x800, rev 0x28, class 0x0) > Feb 04 11:55:50 localhost kernel: bcma: bus0: Core 1 found: IEEE 802.11 > (manuf 0x4BF, id 0x812, rev 0x21, class 0x0) > Feb 04 11:55:50 localhost kernel: bcma: bus0: Core 2 found: PCIe (manuf > 0x4BF, id 0x820, rev 0x16, class 0x0) > Feb 04 11:55:50 localhost kernel: bcma: bus0: Core 3 found: UNKNOWN (manuf > 0x43B, id 0x368, rev 0x00, class 0x0) > Feb 04 11:55:50 localhost kernel: bcma: bus0: Bus registered Which means bcma (bus!) supports BCM43132. It detects bus (!) devices correctly and registers them. There is no driver supporting wireless device found on this chipset. It's a bit like having support for PCI bus. You still need driver for various devices that can be found/connected to such bus. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
