From: vivekanandah@posedge.com
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: Re: adding ba_policy member in drv_ampdu_action op - request information
Date: Thu, 20 Dec 2012 03:55:54 -0800 [thread overview]
Message-ID: <ee2c366af04f45dceda3d3b6d1d130c1@posedge.com> (raw)
In-Reply-To: <1356003605.10029.9.camel@jlt4.sipsolutions.net>
hi johannes,
i agree on that count :)
thanks and regards
Vivek
On Thu, 20 Dec 2012 12:40:05 +0100, Johannes Berg wrote:
> On Thu, 2012-12-20 at 02:39 -0800, vivekanandah@posedge.com wrote:
>
>> is'nt the station's capability and the AP capability intersected
>> during
>> association? i always thought that the comment was mis-represented.
>>
>> i did a small test and i see that the stations capability is
>> actually
>> the subset of AP capabilities that both support.
>> if that is the case, then we do not have to check for the capability
>> independently there! do i miss something in my understanding?
>>
>> also, if what i have stated above is correct, then yes, i feel
>> delayed
>> block ack as a feature might need to be implemented on mac80211 and
>> then
>> check for the same.
>
> I don't see what difference that makes? You still have to implement
> the
> feature fully, we don't have support for it at all.
>
> johannes
>
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-12-20 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 10:18 Re: adding ba_policy member in drv_ampdu_action op - request information vivekanandah
2012-12-13 14:01 ` Johannes Berg
2012-12-20 10:39 ` vivekanandah
2012-12-20 11:40 ` Johannes Berg
2012-12-20 11:55 ` vivekanandah [this message]
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=ee2c366af04f45dceda3d3b6d1d130c1@posedge.com \
--to=vivekanandah@posedge.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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.