From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: ath10k to ath9k IBSS, ath9k has interface-combinations issue
Date: Mon, 06 Apr 2015 17:39:27 -0700 [thread overview]
Message-ID: <5523273F.4060803@candelatech.com> (raw)
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?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2015-04-07 0:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 0:39 Ben Greear [this message]
2015-04-07 5:12 ` ath10k to ath9k IBSS, ath9k has interface-combinations issue Michal Kazior
2015-04-07 5:17 ` Janusz Dziedzic
2015-04-07 16:33 ` Ben Greear
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=5523273F.4060803@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.