Date: Fri, 15 Feb 2013 17:20:26 -0800 From: Adrian Chadd <adrian@freebsd.org> To: PseudoCylon <moonlightakkiy@yahoo.ca> Cc: freebsd-wireless@freebsd.org Subject: Re: negotiating HT params at assoc in sta mode Message-ID: <CAJ-VmonO2Fh1ziVo25Z=BxNHoOzW73TF4LycbQk8ZjL6z=_G=g@mail.gmail.com> In-Reply-To: <CAFZ_MYJqKDRjWMZk%2BuA8ciLSi-W0U6_=gdV4FRKhz%2Bqb6o7qEw@mail.gmail.com> References: <CAFZ_MYJqKDRjWMZk%2BuA8ciLSi-W0U6_=gdV4FRKhz%2Bqb6o7qEw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hm, that sounds right, what's the code doing wrong? Adrian On 15 February 2013 17:09, PseudoCylon <moonlightakkiy@yahoo.ca> wrote: > http://fxr.watson.org/fxr/source/net80211/ieee80211_ht.c?#L2656 > Shouldn't a sta include iv_ampdu_rxmax and iv_ampdu_density instead > when associating? > > 1) A driver initiates iv_ampdu_rxmax and iv_ampdu_density based on h/w > capabilities. > > 2) When a sta trying to associate, > ieee80211_send_mgmt() > { > case IEEE80211_FC0_SUBTYPE_ASSOC_REQ: > ieee80211_add_htcap(); /* the function in question */ > } > > 3) When an ap receives the assoc_req packet, the ap will save ht > params to ni_htparam. Then the ap will use those values for Tx > packets. > > 4) The sta will receive packets which size is within the limits if the > sta included iv_ampdu_rxmax and iv_ampdu_density. > > > AK > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonO2Fh1ziVo25Z=BxNHoOzW73TF4LycbQk8ZjL6z=_G=g>