From: Mahesh Palivela <maheshp@posedge.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] mac80211: VHT peer STA caps
Date: Wed, 26 Sep 2012 22:52:11 +0530 [thread overview]
Message-ID: <506339C3.40405@posedge.com> (raw)
In-Reply-To: <1348660422.10548.10.camel@jlt4.sipsolutions.net>
On 9/26/2012 5:23 PM, Johannes Berg wrote:
>> you mean to say some drivers which dont provide its own VHT caps, will
>> use remote STA VHT caps as its own?
>> If so I feel not correct posing remote STA caps as local caps.
>
> No, no. If you look at HT, then you'll see that if the driver has HT but
> isn't capable of doing everything the peer STA can do, then mac80211
> restricts tells the driver
Sorry. Where is it telling the driver? I couldn't find this part of code
in mac80211, could you point me?
> only about the peer capabilities that the
> device can do as well.
>
> I agree that this isn't really necessary and can be rather complex in
> VHT, but I think you need to document the difference very clearly in the
> documentation for the ieee80211_sta VHT caps.
Can this go as different patch? take my v2 patch as framework. More
implementation of vht.c at later point of time?
>
> johannes
>
--
Thanks,
Mahesh
next prev parent reply other threads:[~2012-09-26 17:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 3:57 [PATCH v2] mac80211: VHT peer STA caps Mahesh Palivela
2012-09-24 8:59 ` Johannes Berg
2012-09-25 5:26 ` Mahesh Palivela
2012-09-25 7:25 ` Johannes Berg
2012-09-25 9:49 ` Mahesh Palivela
2012-09-25 14:09 ` Johannes Berg
2012-09-26 3:15 ` Mahesh Palivela
2012-09-26 11:53 ` Johannes Berg
2012-09-26 17:22 ` Mahesh Palivela [this message]
2012-09-26 17:53 ` Johannes Berg
2012-09-27 3:23 ` Mahesh Palivela
2012-09-27 6:24 ` Johannes Berg
2012-09-27 6:34 ` Mahesh Palivela
2012-09-27 7:01 ` Johannes Berg
2012-09-27 7:21 ` Mahesh Palivela
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=506339C3.40405@posedge.com \
--to=maheshp@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.