From: Johannes Berg <johannes@sipsolutions.net>
To: Peter Oh <poh@codeaurora.org>, Peter Oh <poh@qca.qualcomm.com>,
ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] cfg80211: add VHT support for Mesh
Date: Sun, 15 Nov 2015 15:38:05 +0100 [thread overview]
Message-ID: <1447598285.2554.1.camel@sipsolutions.net> (raw)
In-Reply-To: <5646774D.2000801@codeaurora.org>
On Fri, 2015-11-13 at 15:50 -0800, Peter Oh wrote:
>
> I'm saying, cannot use VHT Mesh by wpa_supplicant because a lack of
> communication method between driver and wpa_supplicant, hence
> extending NL80211 feature flag.
> >
And I'm arguing that you don't need such a communication method since,
unlike IBSS, mesh doesn't restrict the channel width usable further
than the HT/VHT capabilities.
It might, on the other hand, very well be that mesh stuff is missing
some VHT compatibility today - that would be an argument for a more
comprehensive patch that then includes the feature flag to say "we've
fixed the VHT issues in mesh mode". That's quite obviously not what
you're doing though.
johannes
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Peter Oh <poh@codeaurora.org>, Peter Oh <poh@qca.qualcomm.com>,
ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] cfg80211: add VHT support for Mesh
Date: Sun, 15 Nov 2015 15:38:05 +0100 [thread overview]
Message-ID: <1447598285.2554.1.camel@sipsolutions.net> (raw)
In-Reply-To: <5646774D.2000801@codeaurora.org>
On Fri, 2015-11-13 at 15:50 -0800, Peter Oh wrote:
>
> I'm saying, cannot use VHT Mesh by wpa_supplicant because a lack of
> communication method between driver and wpa_supplicant, hence
> extending NL80211 feature flag.
> >
And I'm arguing that you don't need such a communication method since,
unlike IBSS, mesh doesn't restrict the channel width usable further
than the HT/VHT capabilities.
It might, on the other hand, very well be that mesh stuff is missing
some VHT compatibility today - that would be an argument for a more
comprehensive patch that then includes the feature flag to say "we've
fixed the VHT issues in mesh mode". That's quite obviously not what
you're doing though.
johannes
next prev parent reply other threads:[~2015-11-15 14:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 17:59 [PATCH v2] cfg80211: add VHT support for Mesh Peter Oh
2015-11-12 17:59 ` Peter Oh
2015-11-12 20:03 ` Johannes Berg
2015-11-12 20:03 ` Johannes Berg
2015-11-12 21:33 ` Peter Oh
2015-11-12 21:33 ` Peter Oh
2015-11-12 21:40 ` Johannes Berg
2015-11-12 21:40 ` Johannes Berg
2015-11-12 22:28 ` Peter Oh
2015-11-12 22:28 ` Peter Oh
2015-11-12 22:32 ` Johannes Berg
2015-11-12 22:32 ` Johannes Berg
2015-11-12 23:05 ` Peter Oh
2015-11-12 23:05 ` Peter Oh
2015-11-13 7:37 ` Johannes Berg
2015-11-13 7:37 ` Johannes Berg
2015-11-13 23:50 ` Peter Oh
2015-11-13 23:50 ` Peter Oh
2015-11-15 14:38 ` Johannes Berg [this message]
2015-11-15 14:38 ` 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=1447598285.2554.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=poh@codeaurora.org \
--cc=poh@qca.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.