From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Veerendranath Jakkam <quic_vjakkam@quicinc.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] nl80211: Add support to configure allowed frequency list for AP operation
Date: Fri, 31 Mar 2023 12:34:37 +0300 [thread overview]
Message-ID: <ZCapLa6oYIRgF3f4@w1.fi> (raw)
In-Reply-To: <3d09a8c687fc3d37a8be367a518ea174cdc1325d.camel@sipsolutions.net>
On Fri, Mar 31, 2023 at 11:14:14AM +0200, Johannes Berg wrote:
> On Thu, 2023-03-30 at 19:30 +0300, Jouni Malinen wrote:
> Oh, no, I'm entirely happy with this happening in nl80211, it's just the
> age-old question again of whether those upstream drivers will ever even
> get support for it, or if we end up with more code that effectively
> looks dead as far as upstream is concerned :-)
>
> If this actually came with a driver patch using it, the question
> wouldn't even arise, since then it's clear why it's needed and what
> for...
This is one of those cases where the changes seem to be of general
interest, but there is no immediate plans to work on any upstream driver
to use that. As far as the current potentially applicable upstream
drivers are concerned, I would not expect ath6kl to be extended to use
this. I do not really know whether anyone maintaining the drivers for
other vendors would be interested.
This is a balance on what would be the cleanest design (i.e., the most
appropriate nl80211 command for this type of configuration) and
potential help for others vs. what could be done with a somewhat ugly
vendor specific command before the start AP command. Since this specific
case can be handled with a vendor command, I'm not planning on pushing
strongly for this to get accepted into upstream nl80211, but it did seem
to make sense to propose this to see if there would be sufficient
interest for other drivers.
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2023-03-31 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 9:31 [PATCH] nl80211: Add support to configure allowed frequency list for AP operation Veerendranath Jakkam
2023-03-28 9:42 ` Johannes Berg
2023-03-30 16:30 ` Jouni Malinen
2023-03-31 9:14 ` Johannes Berg
2023-03-31 9:34 ` Jouni Malinen [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=ZCapLa6oYIRgF3f4@w1.fi \
--to=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_vjakkam@quicinc.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;
as well as URLs for NNTP newsgroup(s).