From: Eric Appleman <erappleman@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: iwlwifi: Intel 3945ABG speed issues finally identified.
Date: Fri, 24 Dec 2010 22:13:53 +0000 (UTC) [thread overview]
Message-ID: <loom.20101224T222002-889@post.gmane.org> (raw)
In-Reply-To: 1293208648.3997.54.camel@wwguy-huron
So, unless I find something between 2.6.34 release and 2.6.35-rc2 (no changes
between rc1 and rc2), that leaves "fix internal scan", doesn't it?
Btw, this bug is ridiculously hard to test. The early rc kernels for 2.6.35 are
a pain in the ass to test because the iwl3945 driver was in flux at the time. If
I push too hard with speedtests, the driver will cause a kernel panic.
next prev parent reply other threads:[~2010-12-24 22:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 6:15 iwlwifi: Intel 3945ABG speed issues finally identified Eric Appleman
2010-12-23 8:39 ` Eric Appleman
2010-12-23 14:00 ` John W. Linville
2010-12-23 16:13 ` Guy, Wey-Yi
2010-12-23 18:12 ` Eric Appleman
2010-12-24 6:16 ` Eric Appleman
2010-12-24 16:19 ` Guy, Wey-Yi
2010-12-24 2:08 ` Eric Appleman
2010-12-24 16:37 ` Guy, Wey-Yi
2010-12-24 22:13 ` Eric Appleman [this message]
2010-12-28 10:52 ` Stanislaw Gruszka
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=loom.20101224T222002-889@post.gmane.org \
--to=erappleman@gmail.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 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).