From: Mahesh <maheshp@posedge.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
Chakra Parvathaneni <chakra@posedge.com>
Subject: Re: 802.11ac support
Date: Thu, 05 Apr 2012 09:51:56 +0530 [thread overview]
Message-ID: <4F7D1DE4.5000000@posedge.com> (raw)
In-Reply-To: <1333454805.3574.14.camel@jlt3.sipsolutions.net>
On 04/03/2012 05:36 PM, Johannes Berg wrote:
> On Mon, 2012-04-02 at 14:07 +0530, Mahesh wrote:
>
>> I had analysed mac80211 code to see what changes are required for 11ac
>> support. Attached word doc describes mac80211 modules in detail and last
>> section describing what changes we need for 11ac. This is a proposal.
>> Please review and let me know your opinion.
> You really shouldn't try to send word documents to the list, they won't
> arrive anyway. Also, it's bad form to send out documents that say
> "confidential" all over them ...
> Most people also probably don't care about your analysis of what
> mac80211 already does.
>
> In any case, here's my list of things I think will/may need to be done
> for 11ac in the stack:
> * extend regulatory framework (cfg80211)
> * advertise VHT capabilities (nl80211/cfg80211/mac80211& each driver)
> * advertise VHT in scan (mac80211)
> * advertise VHT in assoc req (mac80211)
> * advertise VHT in P2P probe responses (wpa_supplicant)
> * advertise VHT in AP/GO mode beacons/probe responses
> (wpa_supplicant/hostapd)
> * handle per-station VHT capa (mac80211, wpa_s)
> * extended CSA (mac80211)
> * VHT transmit power envelope/extended power constraint (mac80211)
> * quiet channels?
> * HT/VHT basic rate handling?
> * neighbor reports?
> * beamforming action frame support? (mac80211)
>
> johannes
>
Thanks for listing the 11ac requirements. will work on those and post my
updates.
~Mahesh
next prev parent reply other threads:[~2012-04-05 4:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 17:51 [RFC] cfg80211: 80Mhz Bandwidth channel flags in 5Gig band Mahesh
2012-02-22 17:57 ` Johannes Berg
2012-02-22 18:57 ` Johannes Berg
2012-02-24 5:25 ` [RFCv2] " Mahesh
2012-02-24 5:43 ` Adrian Chadd
2012-02-24 5:48 ` Mahesh
2012-02-24 8:01 ` Johannes Berg
2012-02-24 7:55 ` Johannes Berg
2012-02-24 11:21 ` Mahesh
2012-02-25 19:22 ` Adrian Chadd
2012-02-25 21:30 ` Johannes Berg
[not found] ` <eab3dfdc8ebc87ec08ca64db9f237d90@posedge.com>
2012-04-03 12:06 ` 802.11ac support Johannes Berg
2012-04-03 12:11 ` Johannes Berg
2012-04-05 4:21 ` Mahesh [this message]
2012-04-05 14:06 ` Johannes Berg
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=4F7D1DE4.5000000@posedge.com \
--to=maheshp@posedge.com \
--cc=chakra@posedge.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).