On Thu, 2007-05-24 at 00:12 -0700, Michael Wu wrote: > These chunks were present in the second patch of this series. Yup. Will remove. > So, who is going to be responsible for configuring DLS and TS? If we're going > to leave this policy up to userspace.. why not implement most of the DLS > handshake/teardown code in wpa_supplicant directly? It would make the > remaining DLS code in the kernel much more straightforward. Agreed. The end users should never use the debugfs stuff. These symbols are exported for debug and testing. I'd agree to move the policy things to wpa_supplicant. > However, that's still more of an implementation detail. I'm curious about how > DLS would actually get initiated and used if I am, for example, transferring > a large file from one STA to another on the same AP. It seems like the sort > of information needed to make this decision are similar to what is needed to > decide when to set up BA. In the DLS request side, with this patch, you can setup the target MAC address via debugfs "dls_mac" and set 1 to "dls_op" (of course, these will be done by wpa_supplicant in the future). So that mac80211 will initiate DLS setup process. In the receiver side, currently, it accepts or denies the DLS request based on the debugfs "dls_op" value. In the future, the decision should be done by userspace via wpa_supplicant or cfg80211. Thanks, -yi - 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
