linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: Mirco Tischler <mt-ml@gmx.de>
Cc: Arjan van de Ven <arjan@infradead.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"John W.Linville" <linville@tuxdriver.com>,
	"Chatre, Reinette" <reinette.chatre@intel.com>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [2.6.28-rc2]: iwl4965 doesn't connect / cfg80211 failure
Date: Wed, 29 Oct 2008 14:18:04 +0800	[thread overview]
Message-ID: <1225261084.2917.254.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20081028172418.3c8e91f1@mtlp.12.dimension>

[-- Attachment #1: Type: text/plain, Size: 468 bytes --]

On Wed, 2008-10-29 at 00:24 +0800, Mirco Tischler wrote:
> 
> I tested it quickly and not very thoroughly on the wpa-eap encrypted
> network at
> university and it showed the same behaviour: no connection without
> CONFIG_WIRELESS_OLD_REGULATORY and no problems with it enabled.

Interesting. The only difference between without and with
CONFIG_WIRELESS_OLD_REGULATORY is the txpower is lower and you can only
do passive scan. Can you try attached patch?

Thanks,
-yi

[-- Attachment #2: iwlwifi-oldreg-debug.patch --]
[-- Type: text/x-patch, Size: 888 bytes --]

diff --git a/drivers/net/wireless/iwlwifi/iwl-4965.c b/drivers/net/wireless/iwlwifi/iwl-4965.c
index 0953a9c..8123156 100644
--- a/drivers/net/wireless/iwlwifi/iwl-4965.c
+++ b/drivers/net/wireless/iwlwifi/iwl-4965.c
@@ -1523,6 +1523,7 @@ static int iwl4965_send_tx_power(struct iwl_priv *priv)
 		 * the stack trace to find out who is calling this during
 		 * a scan. */
 		IWL_WARNING("TX Power requested while scanning!\n");
+		dump_stack();
 		return -EAGAIN;
 	}
 
diff --git a/net/wireless/reg.c b/net/wireless/reg.c
index 5dab72d..7ffa736 100644
--- a/net/wireless/reg.c
+++ b/net/wireless/reg.c
@@ -71,9 +71,7 @@ static const struct ieee80211_regdomain world_regdom = {
 	.n_reg_rules = 1,
 	.alpha2 =  "00",
 	.reg_rules = {
-		REG_RULE(2412-10, 2462+10, 40, 6, 20,
-			NL80211_RRF_PASSIVE_SCAN |
-			NL80211_RRF_NO_IBSS),
+		REG_RULE(2412-10, 2462+10, 40, 6, 27, 0),
 	}
 };
 

  parent reply	other threads:[~2008-10-29  6:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081028020212.0dfcb6c9@mtlp.12.dimension>
2008-10-28  1:33 ` [2.6.28-rc2]: iwl4965 doesn't connect / cfg80211 failure Zhu Yi
2008-10-28  1:59   ` Mirco Tischler
2008-10-28  2:19     ` Zhu Yi
2008-10-28  3:19       ` Mirco Tischler
2008-10-28  4:32   ` Arjan van de Ven
2008-10-28  5:23     ` Zhu Yi
2008-10-28 16:24       ` Mirco Tischler
2008-10-28 18:36         ` Johannes Berg
2008-10-28 22:58           ` Mirco Tischler
2008-10-28 23:06             ` Johannes Berg
2008-10-28 23:35             ` Mirco Tischler
2008-10-29  6:18         ` Zhu Yi [this message]
2008-10-30 17:24           ` Mirco Tischler
2008-10-30 17:55             ` reinette chatre
2008-10-31 22:25               ` Mirco Tischler
2008-10-28  2:05 ` Mirco Tischler

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=1225261084.2917.254.camel@debian.sh.intel.com \
    --to=yi.zhu@intel.com \
    --cc=arjan@infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mt-ml@gmx.de \
    --cc=reinette.chatre@intel.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).