(resent to list as plain text) Hi, @Dan, yes. Though it's mixed/propietary, it would be great if at least Broadcom would publish specifications for the PHY (LCN40 rev 3) to allow others who are interested (as Rafał Miłecki) to develop open-source drivers. Luckily this time, the issue was in the part of the driver where source is available. -- Frank Vanderham, maintainer of the same driver (wireless-bcm43142) in the AUR, turned my attention to changes suggested by another user (andreyv) on broadcom-wl, also in the AUR. https://aur.archlinux.org/packages.php?ID=19514&comments=all He noticed warnings while compiling the module against kernel 3.6.2: aur-broadcom-wl/src/src/wl/ sys/wl_cfg80211.c:1647:2: warning: initialization from incompatible pointer type [enabled by default] aur-broadcom-wl/src/src/wl/sys/wl_cfg80211.c:1647:2: warning: (near initialization for 'wl_cfg80211_ops.scan') [enabled by default] And noted: --- In Linux's <net/cfg80211.h> we see int (*scan)(struct wiphy *wiphy, struct cfg80211_scan_request *request); but in the module we have static s32 wl_cfg80211_scan(struct wiphy *wiphy, struct net_device *ndev, struct cfg80211_scan_request *request); --- Surely, doing a diff between 3.5.0 and 3.6.0 headers/include/net/cfg80211.h, one notices that net_device was moved to wireless_dev, and subsequently the (second) parameter to cfg80211_scan was dropped. Looking at commits affecting drivers/net/wireless/brcm80211/brcmfmac/ from March onwards, one finds: --- commit fd0142844efa85d89017c89227a0f03de1eee327 Author: Johannes Berg <johannes.berg@xxxxxxxxx> Date: Mon Jun 18 19:17:03 2012 +0200 nl80211: move scan API to wdev The new P2P Device will have to be able to scan for P2P search, so move scanning to use struct wireless_dev instead of struct net_device. --- Adapt a patch (attached) using LINUX_VERSION_CODE conditionals, as to not break support for pre-3.6 kernels, and problem solved. However, scan results seem quite limited. That is, discovered BSSID's are noticeably fewer compared to results on 3.2.x-3.5.x, either via `/sbin/iwlist wlan1 scanning`, or networkmanager. Only 3-5 are show by iwlist, sometimes none, and network manager lists 6 at most. Same driver on 3.5 (or prior) quickly picks up at least 15 BSSIDs. Is there something obviously wrong with the patch? Best, Jasmine On Mon, Oct 1, 2012 at 3:51 PM, Dan Williams <dcbw@xxxxxxxxxx> wrote: > > On Mon, 2012-10-01 at 11:25 +0200, Jasmine Hassan wrote: > > Hi, > > > > I posted this a few days ago against 3.6-rc7, but got no response. > > http://marc.info/?l=linux-wireless&m=134875589522742&w=2 > > > > Tested again today against 3.6 stable, and still triggering kernel bug. > > Attached updated kernel trace from syslog. > > Since that's the closed proprietary driver, there's pretty much nothing > anyone here can do about it, since we don't have the source code. The > ball is in Broadcom's court. > > Dan > -- 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