On Wed, 2009-03-25 at 13:13 +0530, Venkat Ch wrote: > Hi All, > > Last week I have downloaded compat-wireless driver. I have installed > the same into my laptop which has AR242x based WiFi card. Though the > drivers are loaded correctly, the STA (my laptop) did not associate > with the nearby AP. This used to happen well with madwifi driver. > > With my past experience with the details of madwifi driver, I have > browsed through the code base of compat-wireless driver. I observed > that with madwifi driver when the device is made up, the scan process > is kicked off. Where as the same is not happening in compat-wireless. > Does not the scan process need to be kicked off at the end of > ieee80211_open (net/mac80211/iface.c)? A scan gets kicked off when you set either SSID or BSSID using iw or iwconfig, so that the card has some idea of what you'd like to associate with. Kind of pointless to scan on dev open when the card doesn't have any idea of what you want to associate to. Might as well defer that until you _have_ told the card what to do. > Also for ath5k driver, both the hw_scan and sw_scan_start are not > defined. These two functions are used in ieee80211_start_scan to start > the scan process (net/mac80211/scan.c). I observed that the scan > process is not started because the above two functions are not > defined. I believe only Intel Wifi Link cards implement hardware scanning. The rest of the cards use the mac80211 software scan functionality, which works just fine. 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
