linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rajkumar Manoharan <rmanohar@codeaurora.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
	linux-wireless-owner@vger.kernel.org
Subject: Re: [PATCH] cfg80211: propagate iftype HE 6 GHz capability
Date: Tue, 26 May 2020 09:58:45 -0700	[thread overview]
Message-ID: <333b640fcb70004c70918356efdd035b@codeaurora.org> (raw)
In-Reply-To: <8cf15557-2400-0893-9846-f091df7bc457@broadcom.com>

On 2020-05-26 01:10, Arend Van Spriel wrote:
> On 5/26/2020 6:31 AM, Rajkumar Manoharan wrote:
>> Advertise per interface HE 6 GHz band capability to user space
>> which will be used to build IEs.
> 
> I am missing the bigger picture here. It should really be determined
> by the band in which the interface type is operating, right? Can you
> refer to patches on the hostap mailing list relying on this one?
> 
HE capabilities are exposed to user space via NL80211_BAND_IFTYPE_ATTR_*
as each iftype has different set of capabilities. My last series of 
hostapd
6 GHz changes are depending on HT/VHT capability for IE and config 
validation.
Planning to get rid of such dependency by announcing 6 GHz capability by 
driver
and use it in hostapd. Will post hostapd changes sooner.

-Rajkumar


      reply	other threads:[~2020-05-26 16:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26  4:31 [PATCH] cfg80211: propagate iftype HE 6 GHz capability Rajkumar Manoharan
2020-05-26  8:10 ` Arend Van Spriel
2020-05-26 16:58   ` Rajkumar Manoharan [this message]

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=333b640fcb70004c70918356efdd035b@codeaurora.org \
    --to=rmanohar@codeaurora.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless-owner@vger.kernel.org \
    --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).