Return-path: Received: from smtp.codeaurora.org ([198.145.29.96]:47909 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753975AbbKLVeA (ORCPT ); Thu, 12 Nov 2015 16:34:00 -0500 Message-ID: <564505A6.9030001@codeaurora.org> (sfid-20151112_223409_213562_887D6220) Date: Thu, 12 Nov 2015 13:33:26 -0800 From: Peter Oh MIME-Version: 1.0 To: Johannes Berg , Peter Oh , ath10k@lists.infradead.org CC: linux-wireless@vger.kernel.org Subject: Re: [PATCH v2] cfg80211: add VHT support for Mesh References: <1447358605.2131.3.camel@sipsolutions.net> In-Reply-To: <1447358605.2131.3.camel@sipsolutions.net> Content-Type: text/plain; charset=windows-1252; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 11/12/2015 12:03 PM, Johannes Berg wrote: > 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' capability of VHT Mesh. >> In addition to this patch, separate patches to ath10k driver and >> wpa_supplicant are also sent out. >> > Sorry, still doesn't make sense. What does userspace even need to know > this *for*? 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 VHT data rates or not, hence only HT data rates can be used for Mesh Point by userspace now. This patch is introducing NL80211 event to cover the issue. > johannes > > _______________________________________________ > ath10k mailing list > ath10k@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/ath10k Thanks, Peter