On Wed, Dec 20, 2006 at 09:38:20PM -0500, Daniel Drake wrote:
> I don't think that supporting scanning when the interface is supposed to
> be disabled is sensible. If you want to scan, you are simply sending and
> receiving frames, it's no different from having the interface up and
> sending/receiving data frames.
>From a usability point of view, it's helpful to power the card down as
much as possible while it's not being actively used. However, it's also
helpful to be able to provide a list of available wireless networks,
though some degree of latency would be acceptable in that. These two
desires are obviously not entirely compatible with one another, so it
would be helpful if there was some means of providing an intermediate
state.
> 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.
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.
--
Matthew Garrett | [email protected]
-
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]
