From: Shahar Levi <shahar_levi@ti.com>
To: Juuso Oikarinen <juuso.oikarinen@nokia.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Luciano Coelho <luciano.coelho@nokia.com>
Subject: Re: [PATCH ] wl12xx: BA receiver support
Date: Mon, 29 Nov 2010 12:20:31 +0200 [thread overview]
Message-ID: <4CF37E6F.2030409@ti.com> (raw)
In-Reply-To: <1291024275.4284.4443.camel@wimaxnb.nmp.nokia.com>
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@ti.com>
>> ---
[...]
>> + /* 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.
next prev parent reply other threads:[~2010-11-29 10:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 16:33 [PATCH ] wl12xx: BA receiver support Shahar Levi
2010-11-25 9:52 ` Juuso Oikarinen
2010-11-25 11:49 ` Shahar Levi
2010-11-26 9:56 ` Juuso Oikarinen
2010-11-26 16:37 ` Levi, Shahar
2010-11-29 9:51 ` Juuso Oikarinen
2010-11-29 10:20 ` Shahar Levi [this message]
2010-11-29 9:52 ` Luciano Coelho
2010-11-29 10:17 ` Shahar Levi
-- strict thread matches above, loose matches on Subject: below --
2010-11-25 13:51 Shahar Levi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CF37E6F.2030409@ti.com \
--to=shahar_levi@ti.com \
--cc=juuso.oikarinen@nokia.com \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@nokia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.