From: Johannes Berg <johannes@sipsolutions.net>
To: Ramon Fontes <ramonreisfontes@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org
Cc: kvalo@codeaurora.org, davem@davemloft.net
Subject: Re: [PATCH] mac80211_hwsim: report the WIPHY_FLAG_SUPPORTS_5_10_MHZ capability
Date: Mon, 25 May 2020 10:47:43 +0200 [thread overview]
Message-ID: <ab7cac9c73dc8ef956a1719dc090167bcfc24b63.camel@sipsolutions.net> (raw)
In-Reply-To: <20200515164640.97276-1-ramonreisfontes@gmail.com> (sfid-20200515_184649_139967_003E7ED8)
On Fri, 2020-05-15 at 13:46 -0300, Ramon Fontes wrote:
> Signed-off-by: Ramon Fontes <ramonreisfontes@gmail.com>
> ---
> drivers/net/wireless/mac80211_hwsim.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/wireless/mac80211_hwsim.c b/drivers/net/wireless/mac80211_hwsim.c
> index 0528d4cb4..67f97ac36 100644
> --- a/drivers/net/wireless/mac80211_hwsim.c
> +++ b/drivers/net/wireless/mac80211_hwsim.c
> @@ -2995,6 +2995,7 @@ static int mac80211_hwsim_new_radio(struct genl_info *info,
> hw->wiphy->flags |= WIPHY_FLAG_SUPPORTS_TDLS |
> WIPHY_FLAG_HAS_REMAIN_ON_CHANNEL |
> WIPHY_FLAG_AP_UAPSD |
> + WIPHY_FLAG_SUPPORTS_5_10_MHZ |
Not sure this is enough? How about wmediumd, for example?
And also, 5/10 MHz has many more channels inbetween the normal ones, no?
Shouldn't those also be added?
johannes
next prev parent reply other threads:[~2020-05-25 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 16:46 Ramon Fontes
2020-05-25 8:47 ` Johannes Berg [this message]
2020-05-26 11:36 ` Ramon Fontes
2020-05-27 7:54 ` Johannes Berg
2020-05-27 19:14 ` Ramon Fontes
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=ab7cac9c73dc8ef956a1719dc090167bcfc24b63.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ramonreisfontes@gmail.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
all inboxes | Powered by JetHome®