On Wed, 2008-08-06 at 16:56 -0400, Dan Williams wrote: > On Wed, 2008-08-06 at 20:29 +0100, Dave wrote: > > Dan Williams wrote: > > > On Tue, 2008-08-05 at 18:48 -0400, Pavel Roskin wrote: > > >> The userspace is welcome to keep a pool of all APs found by any scans, > > >> but I don't think drivers should do it. > > > > > > Drivers need to keep a reasonably complete list of APs internally for > > > association anyway. You don't want to have to do a full scan just to > > > associate if you have results from 10 seconds ago that are still valid. > > > > This is not an issue for orinoco cards, as the firmware selects the AP to use independently of any driver scanning. The requirement to use ap_scan=2 means that wpa_supplicant doesn't need to look at the scan results either (except maybe to verify the configuration matches). > > Well, since the driver supports SSID scanning, we can use ap_scan=1 > anyway. ap_scan=2 is actually pretty evil since it depends on WEXT > ordering and whatnot. As a follow-up, ap_scan is in practice more about hidden SSID support, and less about roaming. Most firmware handles roaming internally anyway, even if ap_scan=2 is used. The only way to actually disable firmware/driver roaming is to lock the BSSID with SIOCSIWAP. Dan > Dan > > > > Furthermore, drivers need to keep cached results so that two processes > > > can request results of a scan after the scan is complete. > > > > But this does apply to orinoco. > > > > > > Regards, > > > > Dave. > > -- > > 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 > > -- > 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 -- 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
