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
On Thu, 2015-11-12 at 09:59 -0800, Peter Oh wrote:
> Add NL80211_EXT_FEATURE_VHT_MESH flag to allow drivers
> to indicate support for VHT in Mesh mode.
> This flag will be used by wireless drivers to indicate
> the capability of VHT Mesh support and wpa_supplicant to inspect
> wireless drivers'
On Thu, 2015-11-12 at 13:33 -0800, Peter Oh wrote:
>
> At this moment Mesh Point is not able to be brought up by userspace
> such
> as wap_supplicant at VHT data rates because there is no
> events/NL80211
> defined that userspace can check out if drivers can support Mesh
> Point
> (802.11s) at
On 11/12/2015 01:40 PM, Johannes Berg wrote:
On Thu, 2015-11-12 at 13:33 -0800, Peter Oh wrote:
At this moment Mesh Point is not able to be brought up by userspace
such
as wap_supplicant at VHT data rates because there is no
events/NL80211
defined that userspace can check out if drivers can
On 11/12/2015 02:32 PM, Johannes Berg wrote:
On Thu, 2015-11-12 at 14:28 -0800, Peter Oh wrote:
Exactly the same communication mechanism and purpose are used with
NL80211_EXT_FEATURE_VHT_IBSS which is already a part of NL80211
feature
flag.
The new feature flag,
On Thu, 2015-11-12 at 15:05 -0800, Peter Oh wrote:
> On 11/12/2015 02:32 PM, Johannes Berg wrote:
> > On Thu, 2015-11-12 at 14:28 -0800, Peter Oh wrote:
> > >
> > > Exactly the same communication mechanism and purpose are used
> > > with
> > > NL80211_EXT_FEATURE_VHT_IBSS which is already a
On Thu, 2015-11-12 at 14:28 -0800, Peter Oh wrote:
>
> Exactly the same communication mechanism and purpose are used with
> NL80211_EXT_FEATURE_VHT_IBSS which is already a part of NL80211
> feature
> flag.
> The new feature flag, NL80211_EXT_FEATURE_VHT_MESH, follows the same
> purpose and
