All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
	linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net
Subject: Re: [ipw3945-devel] [BUG] iwlwifi 3945 works only with disable_hw_scan=1
Date: Thu, 12 Jun 2008 09:59:36 -0400	[thread overview]
Message-ID: <20080612135936.GA5031@tuxdriver.com> (raw)
In-Reply-To: <1213241315.7814.696.camel@debian.sh.intel.com>

On Thu, Jun 12, 2008 at 11:28:35AM +0800, Zhu Yi wrote:

> I don't understand why "disable_hw_scan=1" works for you. Can you also
> attach the dmesg for it?

How does the hardware scan differ from what mac80211 does when
scanning?  I still see a lot of mysterious iwlwifi (especially iwl3945)
problems in Fedora that seem to disappear with disable_hw_scan=1.

Honestly I'm tempted to change it to "enable_hw_scan" instead...

John
-- 
John W. Linville
linville@tuxdriver.com

  parent reply	other threads:[~2008-06-12 14:07 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11 15:07 [BUG] iwlwifi 3945 works only with disable_hw_scan=1 Maxim Levitsky
2008-06-12  3:28 ` Zhu Yi
2008-06-12 12:13   ` Maxim Levitsky
2008-06-12 13:59   ` John W. Linville [this message]
2008-06-12 14:19     ` [ipw3945-devel] " Maxim Levitsky
2008-06-12 20:25     ` Stephen Clark
2008-06-13  7:35     ` Zhu Yi
2008-06-13  8:48       ` Filippo Zangheri
2008-06-13 12:37         ` Tor Håkon Haugen
2008-06-13 13:03       ` John W. Linville
2008-06-13 14:59         ` Tor Håkon Haugen
2008-06-13 15:06           ` Maxim Levitsky
2008-06-13 15:09             ` Tor Håkon Haugen
2008-06-13 20:04             ` Tomas Winkler
2008-06-14 10:00               ` Maxim Levitsky
2008-06-14 16:50               ` Luis R. Rodriguez
2008-06-15 13:42               ` Maxim Levitsky
2008-06-15 13:47                 ` Tomas Winkler
2008-06-15 14:12                   ` Maxim Levitsky
2008-06-15 15:09                     ` Tomas Winkler
2008-06-15 16:47                       ` Tomas Winkler
2008-06-16  5:50                         ` Maxim Levitsky
2008-06-16  5:52                           ` Tomas Winkler
2008-06-16  6:08                             ` Maxim Levitsky
2008-06-16  6:46                               ` Maxim Levitsky
2008-06-16  7:11                                 ` Maxim Levitsky
2008-06-16 14:35                               ` Dan Williams
2008-06-16 21:41                                 ` Tomas Winkler
2008-06-18  8:28                             ` drago01
2008-06-24 19:47                               ` John W. Linville
2008-06-24 20:32                                 ` Maxim Levitsky
2008-06-25  5:43                                 ` Tomas Winkler
  -- strict thread matches above, loose matches on Subject: below --
2008-06-11 15:47 Maxim Levitsky
2008-06-12  2:26 ` [ipw3945-devel] " Zhu Yi
2008-06-12  6:42   ` drago01
2008-06-12  7:08     ` Zhu Yi
2008-06-12 12:48   ` Maxim Levitsky
2008-06-12 14:22     ` Maxim Levitsky
2008-06-12 14:26       ` Norbert Preining
2008-06-12 15:02     ` Dan Williams
2008-06-13  2:00       ` Zhu Yi
2008-06-13 14:45         ` Dan Williams
2008-06-16  1:40           ` Zhu Yi

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=20080612135936.GA5031@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maximlevitsky@gmail.com \
    --cc=yi.zhu@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 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.