On 02/03/2012 05:06 PM, zefir.kurtisi@xxxxxxxxx wrote: > On 02.02.2012 17:06, Goldenshtein, Victor wrote: >> On Tue, Jan 31, 2012 at 7:43 AM, Johannes Berg >> <johannes@xxxxxxxxxxxxxxxx> wrote: >>> On 1/26/2012 4:37 AM, Victor Goldenshtein wrote: >>>> >>>> The dfs master device should monitor radar channels >>>> for potential radar interference for a minimum of >>>> CAC (channel availability check) time, during this >>>> period no tx can occur. If no radar interference >>>> is detected the dfs master may initiate the tx with >>>> new NL80211_CMD_DFS_ENABLE_TX command. >>> >>> >>> So do we think that no safeguards here at all are acceptable? Not even >>> checking that radar detection was enabled, CAC time expired, etc.? >> >> We can add a check whether dfs is supported by the driver >> (rdev->wiphy.features& NL80211_FEATURE_DFS). >> >> The nl/cfg/mac doesn't have the info whether the radar detection is >> enabled and definitely doesn't heard about CAC time, on other hand the >> driver which starts/handles radar detection know whether it started or >> not. I think the driver should perform this simple "sanity" checks, >> otherwise we"ll need to save different DFS states in the mac, not sure >> that this is what we want. >> >> >> > I noticed this issue working on interfacing ath9k to your DFS > [ ... more unfinished garbage ] Sorry folks for that garbage. My Thunderbird crashed in the middle of writing and for some reason sent out the draft after restart (which I noticed right now). So, what I really wanted to comment is: I noticed this issue working on interfacing ath9k to your DFS management component. When a DFS channel is initially set, the driver has no information whether to block TX or not (as opposed to ap_process_chanswitch() providing these flags). What is the assumption here? Is the driver required to check itself whether a DFS channel is set and raise some internal tx_disabled flag to be reset via hw_dfs_en_tx()? With all the logic being located in hostap, this looks inconsistent (but doable). Aside from that, I managed to interface ath9k to the proposed component. So far, it enables me to set up a DFS monitor to physically test my pattern detectors, while it fails to run in master mode. Need to go through the trace logs to isolate the problem and will report then. Thanks Zefir -- 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
