On 02/01/2011 06:32 PM, John W. Linville wrote: > On Tue, Feb 01, 2011 at 08:38:05AM -0800, Luis R. Rodriguez wrote: >> I though we had reviewed the possibility of moving DFS parameters to >> userspace but it seems that's not the case. We now at least know we >> can keep the DFS regions: US, JP, ETSI, the next step is to determine >> if the DFS parameters for these regions will come from userspace or >> kernelspace. I'm inclined to support starting off with moving this to >> kernelspace just to let us move forward with this support, and once in >> kernel, review the possibility to move this out to userspace. >> >> Thoughts? > > Seems like a reasonable approach for the short term...better than > locking-in userland ABI... > > John Sorry, I was not aware that the userspace DFS approach was already discussed and rejected. I missed two IRC meetings in January and reading [1] sounded to me that potential approaches are still evaluated. Anyhow, I meanwhile posted both approaches (kernel vs. userspace) that are equivalent from functional point, assuming that a HW independent pattern matching is what we need to implement for DFS radar detection. This in fact is still an open issue: Atheros claimed that detection is HW-dependent while we have got up and (maybe not-so-perfectly ;)) running HW-independen radar pattern detection. We are still waiting to get Atheros' pattern detector source code to evaluate detection performance and finally prove the benefit of a HW dependent implementation. Until then (and since the DFS activities degraded lastly) we will continue fine-tuning our detectors based on the proposed design and move to the finally chosen architecture as soon as an agreement is reached. Cheers Zefir [1] http://linuxwireless.org/en/developers/DFS/#DFS_events -- 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
