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 08:45:55 +0530 [thread overview]
Message-ID: <5062736B.9060008@posedge.com> (raw)
In-Reply-To: <1348582152.10041.36.camel@jlt4.sipsolutions.net>
On 09/25/2012 07:39 PM, Johannes Berg wrote:
>
> Well imagine you have a driver for some hardware that can do
> beamforming, and the same driver can also work with hardware that
> doesn't. If we restrict remote caps, like we do for HT, the driver
> doesn't have to worry about this but can just do whatever the remote
> caps say is possible. If we don't restrict it, the driver has to also
> check its own caps.
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.
>
> We can do this, and I suspect it will be simpler, but it needs to be
> *very clearly* documented since VHT will then be different from HT.
>
> johannes
>
next prev parent reply other threads:[~2012-09-26 3:16 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 [this message]
2012-09-26 11:53 ` Johannes Berg
2012-09-26 17:22 ` Mahesh Palivela
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=5062736B.9060008@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.