On 11/29/2010 11:51 AM, Juuso Oikarinen wrote:
On Wed, 2010-11-24 at 18:33 +0200, ext Shahar Levi wrote:
Add new ampdu_action ops to support receiver BA.
The BA initiator session management in FW independently.
Signed-off-by: Shahar Levi<shahar_levi@xxxxxx>
---
[...]
+ /* Single link for now */
+ acx->link_id = 1;
+ acx->tid = tid_index;
+ acx->enable = policy;
+ acx->win_size = 0;
+
Here the window size is configured to 0.
As here the mac80211 does the processing and responding of the add BA
request from the AP, how does the firmware know what window size
eventually was taken into use?
Also, as we already discussed on IRC, the mac80211 currently responds to
the add BA request with the same window size suggested by the AP - in
case of my test AP, this value is 64 - which is too large for the
firmware to cope. So the firmware imposed limit to the window size must
be handled somehow.
-Juuso
you right. as discussed on IRC it should be done on the FW. we still
looking on that.
thanks.
--
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
