linux-wireless.vger.kernel.org archive mirror
 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>
Subject: Re: What would it take to get WDS working with channel contexts?
Date: Fri, 17 Nov 2017 10:45:15 +0100	[thread overview]
Message-ID: <1510911915.2030.37.camel@sipsolutions.net> (raw)
In-Reply-To: <24f85baf-5e19-a2c9-517d-9b69a47860d9@candelatech.com> (sfid-20171117_012807_810321_F19CD790)

On Thu, 2017-11-16 at 16:28 -0800, Ben Greear wrote:
> I have a user interested in getting WDS working on ath10k, but evidently
> this is not supported since ath10k uses channel-contexts:
> 
>  From net/mac80211/main.c:
> 
> 		/*
> 		 * WDS is currently prohibited when channel contexts are used
> 		 * because there's no clear definition of which channel WDS
> 		 * type interfaces use
> 		 */
> 
> 
> Anyone have any suggestions as to how this could be made to work?

You probably don't want to hear this, but:

WDS isn't even properly working without them right now, since for
example there's absolutely no feature negotiation between the peers as
to which rates and other capabilities, bandwidths, etc. are acceptable
(at any given moment in time).

I therefore don't see any value in WDS mode at all unless these issues
are fixed [*], and as such wouldn't want to take any patches that just
do some minimal patching over to allow it with channel contexts.

If you ask me, WDS is entirely useless without vendor-specific
extensions to allow newer features, and the Linux "vendor-specific"
extension to do that is AP/client 4-addr mode.

johannes

[*] and since the spec doesn't define this, you can't even fix them in
any reasonable way, I think, unless you implement some vendor-specific
things that maybe one vendor happens to do.

  reply	other threads:[~2017-11-17  9:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17  0:28 What would it take to get WDS working with channel contexts? Ben Greear
2017-11-17  9:45 ` Johannes Berg [this message]
2017-11-17 16:46   ` Ben Greear
2017-11-27 11:55     ` 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=1510911915.2030.37.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --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 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).