a3767659f0
The fullmac firmware doesn't seem to populate a useful rssi indicator in the RX descriptor, so if one plotted said values, they'd basically look like garbage. The reference driver implements a "get current rssi" firmware command which I guess is really meant for station operation only (as hostap operation would need rssi per station, not a single firmware read.) So: * populate sc_currssi during each calibration run; * use this in the RX path instead of trying to reconstruct the RSSI value and passing it around as a pointer; * do up a quick hack to map the rssi hardware value to some useful signal level; * the survey results provide an RSSI value between 0..100, so just do another quick hack to map it into some usefulish signal level; * supply a faked noise floor - I haven't yet found how to pull it out of the firmware. The scan results and the station RSSI information is now more useful for indicating signal strength / distance. |
||
---|---|---|
.. | ||
if_rsu.c | ||
if_rsureg.h | ||
if_rum.c | ||
if_rumfw.h | ||
if_rumreg.h | ||
if_rumvar.h | ||
if_run.c | ||
if_runreg.h | ||
if_runvar.h | ||
if_uath.c | ||
if_uathreg.h | ||
if_uathvar.h | ||
if_upgt.c | ||
if_upgtvar.h | ||
if_ural.c | ||
if_uralreg.h | ||
if_uralvar.h | ||
if_urtw.c | ||
if_urtwn.c | ||
if_urtwnreg.h | ||
if_urtwreg.h | ||
if_urtwvar.h | ||
if_zyd.c | ||
if_zydfw.h | ||
if_zydreg.h |