Return-path: Received: from s3.sipsolutions.net ([5.9.151.49]:58582 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752196AbaH2LCy (ORCPT ); Fri, 29 Aug 2014 07:02:54 -0400 Message-ID: <1409310171.4577.13.camel@jlt4.sipsolutions.net> (sfid-20140829_130257_704793_9FD7511C) Subject: Re: [PATCHv4 1/2] cfg80211: enable dynack through nl80211 From: Johannes Berg To: Lorenzo Bianconi Cc: linux-wireless , John Linville , Christian Lamparter , Nick Kossifidis Date: Fri, 29 Aug 2014 13:02:51 +0200 In-Reply-To: (sfid-20140812_002559_030837_916613BB) References: <1406556148-3924-1-git-send-email-lorenzo.bianconi83@gmail.com> <1406556148-3924-2-git-send-email-lorenzo.bianconi83@gmail.com> <1407770081.9844.12.camel@jlt4.sipsolutions.net> (sfid-20140812_002559_030837_916613BB) Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: 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? > Anyway documentation should be clearer on that stuff. :) Please extend it then? :) johannes