From: Johannes Berg <johannes@sipsolutions.net>
To: Mahesh Palivela <maheshp@posedge.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linville@tuxdriver.com" <linville@tuxdriver.com>
Subject: Re: [PATCH v2] mac80211: VHT peer STA caps
Date: Tue, 25 Sep 2012 16:09:12 +0200 [thread overview]
Message-ID: <1348582152.10041.36.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <50617E2C.6050000@posedge.com>
On Tue, 2012-09-25 at 15:19 +0530, Mahesh Palivela wrote:
> > OTOH, this would only matter to drivers that actually support all these
> > features, and those drivers could take care of not enabling the features
> > if their hardware doesn't support them. However, think of a driver that
> > is for different hardware, some that supports beamforming and some that
> > doesn't. Then if we mask out the beamforming capability of a station if
> > it's not locally supported, that driver could be simpler? Then again, if
> > we don't the driver just has to check if the hardware supports it, which
> > seems reasonable as well.
> >
> > Do you understand the issue?
> >
>
> why should we mask out remote STA caps bits. Our local hw caps are in
> sband->sta.vht_caps. remote caps sta_info->sta.vht_caps. In what way
> drivers are connected with remote STA vht caps bits.
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.
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-25 14:08 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 [this message]
2012-09-26 3:15 ` Mahesh Palivela
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=1348582152.10041.36.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maheshp@posedge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).