Hi,
presently in code, the block ack policy is not sent by mac80211 to the
lower level driver via the ampdu_action callback.
The mac80211 while transmitting a block ack (ADDBA)request, hardcodes
the block ack methodology to immediate block ack.
on the receive side, the delayed block ack bit is checked along-with
the capability of the receiver station to support delayed block ack.
even if the station supports delayed block ack, mac80211 does not send
the ba_policy down to the driver.
should ba_policy be sent to the driver so that lower level drivers can
take a call as to send block ack response in a delayed manner at its
convenience?
looking forward to some information
thanks in advance
Vivek
On Wed, 2012-12-12 at 12:10 +0530, [email protected] wrote:
> Hi,
>
> presently in code, the block ack policy is not sent by mac80211 to the
> lower level driver via the ampdu_action callback.
>
> The mac80211 while transmitting a block ack (ADDBA)request, hardcodes
> the block ack methodology to immediate block ack.
>
> on the receive side, the delayed block ack bit is checked along-with
> the capability of the receiver station to support delayed block ack.
> even if the station supports delayed block ack, mac80211 does not send
> the ba_policy down to the driver.
>
> should ba_policy be sent to the driver so that lower level drivers can
> take a call as to send block ack response in a delayed manner at its
> convenience?
Well, if you wanted to support it, you'd first have to change the
negotiation to actually ask for it, no?
johannes