.. thinking about it, can you please log some data with ANI disabled and enabled, so we can see exactly what is going on? Something missing (from both freebsd and linux) is visibility into exactly what the ANI code is doing. You can turn on logging to see when the parameters are twiddled, but there's no easy way to log and graph what effect the ANI parameters are having. FreeBSD is slightly ahead here - I can log the tx/rx frames, ofdm/cck phy error rate and then when the parameters are changed; but the driver/HAL doesn't (currently) export what those values are to the athstats program. I think we'd all be better off if we had some tools to graph/analyse this kind of stuff; we could then figure out if it's having any kind of effect. Thanks for chasing this up! I'm currently hacking on my openwrt (sort of) inspired build system for FreeBSD, targetting an AR913x device. So this is quite relevant to me at the present moment. :) Adrian -- 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
