linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: Michal Kazior <michal.kazior@tieto.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath10k to ath9k IBSS, ath9k has interface-combinations issue
Date: Tue, 07 Apr 2015 09:33:40 -0700	[thread overview]
Message-ID: <552406E4.50600@candelatech.com> (raw)
In-Reply-To: <CALhHN=oCvQ=SvobWTvc3geK-66k2+YDzB1HqSguCxTeV0QzWwg@mail.gmail.com>

On 04/06/2015 10:17 PM, Janusz Dziedzic wrote:
> On 7 April 2015 at 07:12, Michal Kazior <michal.kazior@tieto.com> wrote:
>> On 7 April 2015 at 02:39, Ben Greear <greearb@candelatech.com> 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 <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2015-04-07 16:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07  0:39 ath10k to ath9k IBSS, ath9k has interface-combinations issue Ben Greear
2015-04-07  5:12 ` Michal Kazior
2015-04-07  5:17   ` Janusz Dziedzic
2015-04-07 16:33     ` Ben Greear [this message]
2015-04-07 17:35       ` Ben Greear
2015-04-08  3:25         ` Sujith Manoharan
2015-04-10  5:47           ` Sven-Ola Tuecke
2015-04-17  0:11           ` Ben Greear
2015-04-24 14:42             ` Sujith Manoharan
2015-04-24 15:36               ` Ben Greear

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=552406E4.50600@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=janusz.dziedzic@tieto.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michal.kazior@tieto.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).