All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	ath10k <ath10k@lists.infradead.org>
Subject: Re: VHT 160Mhz and nss related config.
Date: Mon, 13 Feb 2017 20:51:29 +0100	[thread overview]
Message-ID: <1487015489.19813.9.camel@sipsolutions.net> (raw)
In-Reply-To: <0f30d7bf-b710-10a8-91e6-bfd75457cf75@candelatech.com>

On Mon, 2017-02-13 at 11:42 -0800, Ben Greear wrote:
> On 02/13/2017 11:37 AM, Johannes Berg wrote:
> > 
> > > > This was recently added to the VHT capabilities in the spec,
> > > > see
> > > > Table 9-250 in 802.11-2016.
> > > I don't have that spec...maybe you could post a patch that adds
> > > that
> > > flag and/or other fields to the appropriate header files?  I can
> > > attempt to add support to ath10k after that...
> > 
> > We're planning to, but it's not the most important thing on my list
> > right now ... I'll check where that's at now.
> > 
> > I can't even easily explain it, since it's really complicated.
> 
> So, think it is worthwhile to use the max-rx-rate as a proxy
> until the 'real' spec is implemented?  If 2x2 160Mhz is super
> complicated, and yields no useful throughput improvement, then likely
> it will be a long time before someone implements it properly I'd
> guess.

I don't know, I haven't really followed that discussion.

I don't think implementing the spec here will be really complicated,
there are just a bunch of cases to consider when parsing the VHT
capabilities. I won't do anything with max rate in mac80211, and I
doubt you really should implement any workarounds for not having the
spec here in the driver itself.

johannes

WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	ath10k <ath10k@lists.infradead.org>
Subject: Re: VHT 160Mhz and nss related config.
Date: Mon, 13 Feb 2017 20:51:29 +0100	[thread overview]
Message-ID: <1487015489.19813.9.camel@sipsolutions.net> (raw)
In-Reply-To: <0f30d7bf-b710-10a8-91e6-bfd75457cf75@candelatech.com>

On Mon, 2017-02-13 at 11:42 -0800, Ben Greear wrote:
> On 02/13/2017 11:37 AM, Johannes Berg wrote:
> > 
> > > > This was recently added to the VHT capabilities in the spec,
> > > > see
> > > > Table 9-250 in 802.11-2016.
> > > I don't have that spec...maybe you could post a patch that adds
> > > that
> > > flag and/or other fields to the appropriate header files?  I can
> > > attempt to add support to ath10k after that...
> > 
> > We're planning to, but it's not the most important thing on my list
> > right now ... I'll check where that's at now.
> > 
> > I can't even easily explain it, since it's really complicated.
> 
> So, think it is worthwhile to use the max-rx-rate as a proxy
> until the 'real' spec is implemented?  If 2x2 160Mhz is super
> complicated, and yields no useful throughput improvement, then likely
> it will be a long time before someone implements it properly I'd
> guess.

I don't know, I haven't really followed that discussion.

I don't think implementing the spec here will be really complicated,
there are just a bunch of cases to consider when parsing the VHT
capabilities. I won't do anything with max rate in mac80211, and I
doubt you really should implement any workarounds for not having the
spec here in the driver itself.

johannes

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2017-02-13 19:51 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 22:58 VHT 160Mhz and nss related config Ben Greear
2017-02-10 22:58 ` Ben Greear
     [not found] ` <CAJ-Vmo=-JBrkmUPcYrRbARYuWv_=-MeQpPwAN_0J3v8pA5mPnw@mail.gmail.com>
2017-02-10 23:26   ` Ben Greear
2017-02-10 23:26     ` Ben Greear
2017-02-11  4:22 ` Sebastian Gottschall
2017-02-11  4:22   ` Sebastian Gottschall
2017-02-11  4:37   ` Adrian Chadd
2017-02-11  4:37     ` Adrian Chadd
2017-02-11 17:58     ` Ben Greear
2017-02-11 17:58       ` Ben Greear
2017-02-11 18:21       ` Sebastian Gottschall
2017-02-11 18:21         ` Sebastian Gottschall
2017-02-11 19:38         ` Ben Greear
2017-02-11 19:38           ` Ben Greear
2017-02-12 10:56           ` Sebastian Gottschall
2017-02-12 10:56             ` Sebastian Gottschall
2017-02-12 16:05             ` Ben Greear
2017-02-12 16:05               ` Ben Greear
2017-02-12 20:21               ` Sebastian Gottschall
2017-02-12 20:21                 ` Sebastian Gottschall
2017-02-13 19:56         ` Ben Greear
2017-02-13 19:56           ` Ben Greear
2017-02-13 21:19           ` Sebastian Gottschall
2017-02-13 21:19             ` Sebastian Gottschall
2017-02-13 22:48           ` Sebastian Gottschall
2017-02-13 22:48             ` Sebastian Gottschall
2017-02-13 23:12             ` Ben Greear
2017-02-13 23:12               ` Ben Greear
2017-02-14 10:19               ` Sebastian Gottschall
2017-02-14 10:19                 ` Sebastian Gottschall
2017-02-13  7:06 ` Johannes Berg
2017-02-13  7:06   ` Johannes Berg
2017-02-13 19:21   ` Ben Greear
2017-02-13 19:21     ` Ben Greear
2017-02-13 19:27     ` Adrian Chadd
2017-02-13 19:27       ` Adrian Chadd
2017-02-13 19:37     ` Johannes Berg
2017-02-13 19:37       ` Johannes Berg
2017-02-13 19:42       ` Ben Greear
2017-02-13 19:42         ` Ben Greear
2017-02-13 19:51         ` Johannes Berg [this message]
2017-02-13 19:51           ` 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=1487015489.19813.9.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ath10k@lists.infradead.org \
    --cc=greearb@candelatech.com \
    --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.