summaryrefslogtreecommitdiffstats
path: root/usr.bin
diff options
context:
space:
mode:
authoradrian <adrian@FreeBSD.org>2012-02-06 20:23:21 +0000
committeradrian <adrian@FreeBSD.org>2012-02-06 20:23:21 +0000
commit021c66f70f01c3bec51cbc8897f52d79fc09569b (patch)
tree1d58c6dd7c3291b76b56b4ae526ee6dd438a2aa4 /usr.bin
parente53a6745b5c1e294f4615a8bc6699cdcc8e287ae (diff)
downloadFreeBSD-src-021c66f70f01c3bec51cbc8897f52d79fc09569b.zip
FreeBSD-src-021c66f70f01c3bec51cbc8897f52d79fc09569b.tar.gz
Contribute some example code which demonstrates how to initialise the
radar parameters for the AR5416 and later NICs. These parameters have been tested on the following NICs: * AR5416 * AR9160 * AR9220 * AR9280 And yes, these will return radar pulse parameters and (for AR9160 and later) radar FFT information as PHY errors. This is again not enough to do radar detection, it's just here to faciliate development and validation of radar detection algorithms. The (pulse, not FFT) decoding code for AR5212, AR5416 and later NICs exist in the HAL. This code is disabled for now as generating radar PHY errors can quickly cause issues in busy environment.s Some further debugging of the RX path is needed. Finally, these parameters are likely not useful for the AR5212 era NICs. The madwifi-dfs branch should have suitable example parameters for the 11a era NICs.
Diffstat (limited to 'usr.bin')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud