All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: Re: VHT support, take 2
Date: Fri, 09 Nov 2012 21:21:33 +0100	[thread overview]
Message-ID: <1352492493.28302.7.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1352492254-29399-1-git-send-email-johannes@sipsolutions.net> (sfid-20121109_211702_930840_209B43F6)

On Fri, 2012-11-09 at 21:17 +0100, Johannes Berg wrote:

> What I intend to do next is this have a patch to parse the VHT
> operation IE in mac80211 (or have a helper in cfg80211?) to
> select the VHT channel configuration in MLME code.
> 
> I'm kinda hoping the posedge folks will come back with the
> regulatory code so I don't have to worry about that ...
> *hint hint* :-)
> 
> After that, I'll need to work on the remaining hostapd code,
> that should just need channel configuration etc. now. Then I
> think it just needs a good test run.
> 
> I'm not interested in VHT IBSS, so I'm not going to do anything
> there, nor VHT mesh.
> 
> The other thing would be rate control, e.g. minstrel_vht, but
> I'm not sure we can use minstrel at all, so I'll probalby not
> work on minstrel myself.

Oh and then of course there's also a whole bunch of action frame
handling that will be needed in mac80211, but I'm not really sure yet
what that actually is.

johannes


  parent reply	other threads:[~2012-11-09 20:20 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-09 20:17 VHT support, take 2 Johannes Berg
2012-11-09 20:17 ` [RFC v2 1/8] cfg80211: remove remain-on-channel channel type Johannes Berg
2012-11-09 20:17 ` [RFC v2 2/8] nl80211: add documentation for " Johannes Berg
2012-11-15 11:00   ` Mahesh Palivela
2012-11-15 12:09     ` Johannes Berg
2012-11-09 20:17 ` [RFC v2 3/8] cfg80211: pass a channel definition struct Johannes Berg
2012-11-09 20:17 ` [RFC v2 4/8] nl80211/cfg80211: support VHT channel configuration Johannes Berg
2012-11-12 10:55   ` Johannes Berg
2012-11-16 12:21   ` Mahesh Palivela
2012-11-16 12:37     ` Johannes Berg
2012-11-19  4:18       ` Mahesh Palivela
2012-11-19  8:33         ` Johannes Berg
2012-11-19 12:18   ` Mahesh Palivela
2012-11-19 14:11     ` Johannes Berg
2012-11-20  6:03       ` Mahesh Palivela
2012-11-20  7:27         ` Johannes Berg
2012-11-20  8:27   ` Mahesh Palivela
2012-11-20  8:41     ` Johannes Berg
2012-11-20  9:39       ` Johannes Berg
2012-11-20 11:59         ` Mahesh Palivela
2012-11-20 12:21           ` Johannes Berg
2012-11-20 12:56             ` Mahesh Palivela
2012-11-09 20:17 ` [RFC v2 5/8] mac80211: convert to channel definition struct Johannes Berg
2012-11-09 20:17 ` [RFC v2 6/8] nl80211/cfg80211: add VHT MCS support Johannes Berg
2012-11-09 20:17 ` [RFC v2 7/8] mac80211: support drivers reporting VHT RX Johannes Berg
2012-11-09 20:17 ` [RFC v2 8/8] mac80211: support VHT rates in TX info Johannes Berg
2012-11-09 20:21 ` Johannes Berg [this message]
2012-11-15 12:09   ` VHT support, take 2 Mahesh Palivela
2012-11-16 13:28     ` Johannes Berg
2012-11-16 14:57       ` Arend van Spriel
2012-11-17  0:10         ` Luis R. Rodriguez
2012-11-17  8:48           ` Johannes Berg
2012-11-17 23:34             ` Luis R. Rodriguez
2012-11-18 11:03               ` Johannes Berg
2012-11-18 11:05                 ` 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=1352492493.28302.7.camel@jlt4.sipsolutions.net \
    --to=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.