Comment 10 for bug 1311462

Hm, so apparently as far as network manager is concerned, the chipset doesn't support N; I guess network manager simply doesn't care and just asks the driver to connect to networks. I don't think NM cares about the protocol, really; I don't see that specified anywhere when setting up a connection.

I don't think we can really fix this one if the driver is not reporting its capabilities correctly. We could try coming up with some sort of workaround or heuristic.

We know broadcom chips misreport this, we can compile a list of broadcom PCI IDs that are supposed to support N, and if the card matches one of those, we just blindly report "n". This is better than reporting "n" support for ALL broadcom chipsets.

It's a bit more work for us but it may be the most reliable solution.