linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: reinette chatre <reinette.chatre@intel.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: 2.6.28-rc regression: Can't stop Rx DMA
Date: Wed, 29 Oct 2008 10:10:52 -0700	[thread overview]
Message-ID: <1225300252.1115.266.camel@rc-desk> (raw)
In-Reply-To: <20081029002713.GA16554@isilmar.linta.de>

On Tue, 2008-10-28 at 17:27 -0700, Dominik Brodowski wrote:
> With CONFIG_WIRELESS_OLD_REGULATORY=y, both the old and the new firmware
> works. Without, only the old firmware works.

(I assume you mean "only the new firmware works")

> 
> I'd think that at least the error message could be clarified a bit
> (is it really a "Microcode SW error"?)... also, it might be a corner case
> whether the new firmware would better be called -2 because of this
> incompatibility?

We can do away with the error message with a driver change. This patch
should take care of it:

diff --git a/drivers/net/wireless/iwlwifi/iwl3945-base.c b/drivers/net/wireless/iwlwifi/iwl3945-base.c
index 0758f8f..ab7c93d 100644
--- a/drivers/net/wireless/iwlwifi/iwl3945-base.c
+++ b/drivers/net/wireless/iwlwifi/iwl3945-base.c
@@ -6219,6 +6219,11 @@ static void iwl3945_bg_request_scan(struct work_struct *data)
 					      n_probes,
 			(void *)&scan->data[le16_to_cpu(scan->tx_cmd.len)]);
 
+	if (scan->channel_count == 0) {
+		IWL_DEBUG_SCAN("channel count %d\n", scan->channel_count);
+		goto done;
+	}
+
 	cmd.len += le16_to_cpu(scan->tx_cmd.len) +
 	    scan->channel_count * sizeof(struct iwl3945_scan_channel);
 	cmd.data = scan;



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

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-18 23:10 2.6.28-rc regression: Can't stop Rx DMA Dominik Brodowski
2008-10-18 23:30 ` Tomas Winkler
2008-10-19  7:59   ` Dominik Brodowski
2008-10-27 20:02     ` reinette chatre
2008-10-27 20:24       ` reinette chatre
2008-10-27 22:11     ` reinette chatre
2008-10-27 23:03       ` Dominik Brodowski
2008-10-28  0:47         ` reinette chatre
     [not found]           ` <20081028194323.GA14303@isilmar.linta.de>
2008-10-28 20:23             ` reinette chatre
2008-10-28 23:15               ` Johannes Berg
2008-10-28 23:32                 ` reinette chatre
2008-10-28 23:38                   ` Dominik Brodowski
2008-10-29  0:27                     ` Dominik Brodowski
2008-10-29 10:01                       ` Dan Williams
2008-10-29 17:10                       ` reinette chatre [this message]
2008-10-29 21:53                         ` Dominik Brodowski
2008-10-29 23:06                           ` reinette chatre
2008-10-29 11:48                   ` Johannes Berg
2008-10-29 15:37                     ` reinette chatre

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=1225300252.1115.266.camel@rc-desk \
    --to=reinette.chatre@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    /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).