> Hi, > > Sorry for the delay. > >> dynack is disable by default at bootstrap and it is automatically >> disabled as soon as you set coverage_class (coverage_class >= 0) after >> dynack has been enabled (coverage_class = -1). E.g: >> >> - iw phy phy0 set distance auto (to enable dynack) >> >> - iw phy phy0 set distance x (to set coverage class and disable dynack) >> >> >> This logic is implemented in dynack code. Is it fine for you? > > Ok, I guess that's reasonable. The default coverage class is 0 I guess? Yes, dynack is disabled at bootstrap and default coverage class is 0 > >> Anyway documentation should be clearer on that stuff. :) > > Please extend it then? :) > I will send a new patchset with more comments on that stuff :) > johannes > Regards, Lorenzo -- UNIX is Sexy: who | grep -i blonde | talk; cd ~; wine; talk; touch; unzip; touch; strip; gasp; finger; gasp; mount; fsck; more; yes; gasp; umount; make clean; sleep -- 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
