From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Berg Date: Tue, 16 Jun 2015 09:08:40 +0200 Subject: [ath9k-devel] [RFC] ath9k: advertise p2p dev support when chanctx In-Reply-To: (sfid-20150616_083056_853720_6BA9919F) References: <1433913034-17801-1-git-send-email-janusz.dziedzic@tieto.com> <21886.43539.833126.629494@gargle.gargle.HOWL> <21886.62363.946771.345441@gargle.gargle.HOWL> <557F1716.3040204@broadcom.com> <21887.31486.302760.504336@gargle.gargle.HOWL> (sfid-20150616_083056_853720_6BA9919F) Message-ID: <1434438520.2337.7.camel@sipsolutions.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Tue, 2015-06-16 at 08:30 +0200, Janusz Dziedzic wrote: > Other fix I can image is change wpa_supplicant and add > NL80211_SCAN_FLAG_AP to p2p_find, and set in ath9k driver > wiphy->features |= NL80211_FEATURE_AP_SCAN; > > NL80211_FEATURE_AP_SCAN is not set when use_chanctx=1 > > I am not sure which is better. First one required only fix in ath9k, > second one also required changes in wpa_supplicant. It would be unfortunate if a driver change required wpa_s changes. It doesn't seem so bad to add p2p-device support to the driver, after all, there isn't much it needs to do for that. This seems like a strange quirk though - you can normally not do any p2p operation when already operating as soft-AP (without P2P-device), no? johannes