Matthew Garrett wrote:
There are additional implementation problems: scanning requires 2
different ioctl calls: siwscan, then several giwscan. If you want the
driver to effectively temporarily bring the interface up when userspace
requests a scan but the interface was down, then how does the driver
know when to bring it down again?
Hm. Does the spec not set any upper bound on how long it might take for
APs to respond? I'm afraid that my 802.11 knowledge is pretty slim.
I'm not sure, but thats not entirely relevant either. The time it takes
for the AP to respond is not related to the delay between userspace
sending the siwscan and giwscan ioctls (unless you're thinking of
userspace being too quick, but GIWSCAN already returns -EINPROGRESS when
appropriate so this is detectable)
Picking a number out of thin air would be one answer, but clearly less
than ideal. This may be a case of us not being able to satisfy everyone,
and so just having to force the user to choose between low power or
wireless scanning.
I think it's reasonable to keep the interface down, but then when the
user does want to connect, bring the interface up, scan, present scan
results. Scanning is quick, there would be minimal wait needed here.
Alternatively, if you do want to prepare scan results in the background
every 2 minutes, use a sequence something like:
- bring interface up
- siwscan
- giwscan [...]
- bring interface down
- repeat after 2 mins
If this kind of thing was implemented at the driver level, in most cases
it would be identical to doing the above anyway.
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
