linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Krishna Chaitanya <chaitanya.mgit@gmail.com>, Jouni Malinen <j@w1.fi>
Cc: Ben Greear <greearb@candelatech.com>,
	"Valo, Kalle" <kvalo@qca.qualcomm.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] ath10k: remove VHT capabilities from 2.4GHz
Date: Wed, 27 Apr 2016 11:45:05 +0200	[thread overview]
Message-ID: <1461750305.3723.9.camel@sipsolutions.net> (raw)
In-Reply-To: <CABPxzYJz59wOXjK2fCK_Tp05g0g1FY+VWscFKz9fG+D1swZGBA@mail.gmail.com> (sfid-20160427_113746_741811_8AD5A5E1)

On Wed, 2016-04-27 at 15:07 +0530, Krishna Chaitanya wrote:
> 
> If many vendors need this support, then mac80211 appraoch would be
> good. If not, we should stick to driver approach.

Trying to do this in the driver gets practically impossible, so no, it
really should be done in mac80211 either way. Drivers have to opt in by
reporting VHT caps for 2.4 GHz, at which point we simply revert this
patch, but get the right over-the-air behaviour.

johannes

  reply	other threads:[~2016-04-27  9:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 13:17 [PATCH v2] ath10k: remove VHT capabilities from 2.4GHz Kalle Valo
2016-04-21 15:15 ` Ben Greear
2016-04-26  7:04   ` Johannes Berg
2016-04-26 12:03     ` Valo, Kalle
2016-04-26 20:07       ` Krishna Chaitanya
2016-04-26 20:10         ` Ben Greear
2016-04-27  6:43           ` Krishna Chaitanya
2016-04-27  9:16             ` Jouni Malinen
2016-04-27  9:37               ` Krishna Chaitanya
2016-04-27  9:45                 ` Johannes Berg [this message]
2016-05-06 18:08 ` Valo, Kalle

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=1461750305.3723.9.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ath10k@lists.infradead.org \
    --cc=chaitanya.mgit@gmail.com \
    --cc=greearb@candelatech.com \
    --cc=j@w1.fi \
    --cc=kvalo@qca.qualcomm.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 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).