From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: fix ibss scanning
Date: Wed, 12 Dec 2012 08:26:57 +0100 [thread overview]
Message-ID: <20121212072656.GA2253@redhat.com> (raw)
In-Reply-To: <1355256114.9819.19.camel@jlt4.sipsolutions.net>
On Tue, Dec 11, 2012 at 09:01:54PM +0100, Johannes Berg wrote:
> On Tue, 2012-12-11 at 10:48 +0100, Stanislaw Gruszka wrote:
> > Do not scan on no-IBSS and disabled channels in IBSS mode. Doing this
> > can trigger Microcode errors on iwlwifi and iwlegacy drivers.
>
> I guess this makes sense regardless of the microcode errors, applied.
> (Are you using SW scan?)
On iwlwifi error triggers with HW scan, on iwlegacy (3945) with SW
scan.
Thanks
Stanislaw
prev parent reply other threads:[~2012-12-12 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 9:48 [PATCH] mac80211: fix ibss scanning Stanislaw Gruszka
2012-12-11 20:01 ` Johannes Berg
2012-12-12 7:26 ` Stanislaw Gruszka [this message]
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=20121212072656.GA2253@redhat.com \
--to=sgruszka@redhat.com \
--cc=johannes@sipsolutions.net \
--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 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).