On 02/27/13 18:44, Arend van Spriel wrote: >> I think the best approach here is to allow the higher layers to hint to >> the driver that some operations that are about to start must be "more >> reliable". That includes EAPOL, DHCP, IP autoconfiguration, etc. Then >> when the higher layers know the operation is finished, they can indicate >> the operations are done and the driver can go do whatever it wants. > > Indeed the RFC approach was explicit about the scope of this interface being BT coex or actually BT > coex override. Johannes proposes one dedicated to DHCP as a similar interface in Android is used for > that right now. Abstracting it to "more reliable" mainly avoids renaming it when someone comes up > with a use-case other than BT coex or DHCP. Definitely a more generic interface would be great as there are many driver independent things that can be done to improve "reliability" (defer scanning, prevent band/channel switching). But I think it is a good idea to keep this "reliability boost" time constrained on cfg80211 level, with userspace signaling that it is done resulting in return to default operation earlier. Piotr -- 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
