Return-path: Received: from mail2.candelatech.com ([208.74.158.173]:59897 "EHLO mail2.candelatech.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753736AbbDGQdl (ORCPT ); Tue, 7 Apr 2015 12:33:41 -0400 Message-ID: <552406E4.50600@candelatech.com> (sfid-20150407_183346_718883_53B7D9C0) Date: Tue, 07 Apr 2015 09:33:40 -0700 From: Ben Greear MIME-Version: 1.0 To: Janusz Dziedzic CC: Michal Kazior , "linux-wireless@vger.kernel.org" Subject: Re: ath10k to ath9k IBSS, ath9k has interface-combinations issue References: <5523273F.4060803@candelatech.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 04/06/2015 10:17 PM, Janusz Dziedzic wrote: > On 7 April 2015 at 07:12, Michal Kazior wrote: >> On 7 April 2015 at 02:39, Ben Greear wrote: >>> Has anyone tried running ath10k to ath9k IBSS? >>> >>> I'm trying this with a somewhat hacked 4.0-rc6 kernel, >>> and latest wpa_supplicant. >>> >>> ath9k to ath9k works with and without encryption, and ath10k to ath10k works >>> (w/out encryption at least). >>> >>> But, if I try to tell ath10k to connect to ath9k, then the ath9k reports >>> interface combinations >>> issues and will not associate. I've added some debug, and the issue is the >>> 'num==0' part here: >>> >>> >>> int cfg80211_check_combinations(struct wiphy *wiphy, >>> const int num_different_channels, >>> const u8 radar_detect, >>> const int iftype_num[NUM_NL80211_IFTYPES]) >>> { >>> int err, num = 0; >>> >>> err = cfg80211_iter_combinations(wiphy, num_different_channels, >>> radar_detect, iftype_num, >>> cfg80211_iter_sum_ifcombs, &num); >>> if (err) { >>> pr_info("cfg-comb-check: failed to iterate combinations\n"); >>> return err; >>> } >>> if (num == 0) { >>> pr_info("cfg-comb-check: iter-combinations returned >>> num==0\n"); >>> return -EBUSY; >>> } >>> >>> return 0; >>> } >>> EXPORT_SYMBOL(cfg80211_check_combinations); >>> >>> There should be exactly one interface on this radio that is admin-up, and it >>> is the >>> one that I am trying to make run in adhoc mode. >>> >>> Any ideas on this? >> >> IBSS with non-fixed or dfs channel? It would bump >> num_different_channels and yield no valid combinations. But why would >> that work fine with, e.g. ath9k-ath9k otherwise - no idea. >> > > Check this discussion (ibss + p2p_device - this could be one you hit). > http://www.spinics.net/lists/linux-wireless/msg134447.html That patch is in my tree already, so must be something else. Thanks, Ben > > BR > Janusz > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Ben Greear Candela Technologies Inc http://www.candelatech.com