On Tue, 2008-08-05 at 17:55 -0400, Dan Williams wrote: > On Tue, 2008-08-05 at 17:15 -0400, Pavel Roskin wrote: > > If I use 32-bit kernel with 32-bit userspace, essid filtering works, but > > only to a degree. Old scan results are cached somewhere, so if I scan > > with essid and then without essid, I get filtered results. Likewise, If > > I don't use filtering the first time, but use it the second time, I get > > unfiltered results. > > Scanning for a specific SSID never has "filtered" the results, nor > should it. It just probe-scans the requested SSID and return any new > results in with the cached ones. You requested an SSID scan, thus you > must know the SSID, thus you can do the filtering yourself? Perhaps I used a wrong word. If requesting a scan, I expect to get results from a scan with the parameters I supplied. If the scan results are from a scan with different parameters, I don't want them. I'd rather see the driver return EAGAIN than results of a scan with different parameters. The userspace is welcome to keep a pool of all APs found by any scans, but I don't think drivers should do it. I believe it was discussed before. If there was any decision how we want drivers to behave, let's stick with it. -- Regards, Pavel Roskin -- 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
