From: "John W. Linville" <linville@tuxdriver.com>
To: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [PATCH 1/6] iwlwifi: schedule to deprecate software scan support
Date: Wed, 6 Oct 2010 15:03:43 -0400 [thread overview]
Message-ID: <20101006190343.GI2472@tuxdriver.com> (raw)
In-Reply-To: <1286387500.12594.24.camel@wwguy-ubuntu>
On Wed, Oct 06, 2010 at 10:51:40AM -0700, Guy, Wey-Yi wrote:
> On Wed, 2010-10-06 at 10:36 -0700, John W. Linville wrote:
> > On Wed, Oct 06, 2010 at 08:23:08AM -0700, Wey-Yi Guy wrote:
> > > Hardware scan is the prefer method for all iwlwifi devices;
> > > especially for dual-mode functions. Schedule to deprecate the
> > > software scan support in kernel 2.6.40
> > >
> > > Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> >
> > Hmmm...perhaps you have more confidence in this than I do?
> > My experience suggests that hardware scanning has been the source of
> > a number of problems and having the option to turn it off has provided
> > a useful workaround for any number of users.
> >
> > Anyone else have heartburn over this one?
> >
> The current HW scan implementation was improve a lot and sw scan will
> cause problem, especially once we introduce P2P.
What support issues are caused by supporting software scanning?
Whatever issues are caused by scanning with P2P, doesn't mac80211
have to handle them anyway?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-10-06 19:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 15:23 [PATCH 0/6] update for 2.6.37 Wey-Yi Guy
2010-10-06 15:23 ` [PATCH 1/6] iwlwifi: schedule to deprecate software scan support Wey-Yi Guy
2010-10-06 17:36 ` John W. Linville
2010-10-06 17:48 ` Johannes Berg
2010-10-06 17:51 ` Guy, Wey-Yi
2010-10-06 19:03 ` John W. Linville [this message]
2010-10-06 19:43 ` Guy, Wey-Yi
2010-10-07 8:39 ` Johannes Berg
2010-10-07 18:04 ` John W. Linville
2010-10-07 18:31 ` [ipw3945-devel] " Daniel Halperin
2010-10-07 18:36 ` Johannes Berg
2010-10-06 15:23 ` [PATCH 2/6] iwlagn: reduce redundant parameter definitions Wey-Yi Guy
2010-10-06 15:23 ` [PATCH 3/6] iwlagn: rename iwl5000_tx_power_dbm_cmd Wey-Yi Guy
2010-10-06 15:23 ` [PATCH 4/6] iwlwifi: remove uncorrect comments Wey-Yi Guy
2010-10-06 15:23 ` [PATCH 5/6] iwlagn: rename iwl5000_tx_resp Wey-Yi Guy
2010-10-06 15:23 ` [PATCH 6/6] iwlagn: define 130 series of WiFi/BT combo devices Wey-Yi Guy
2010-10-06 23:28 ` Julian Calaby
2010-10-06 23:32 ` Guy, Wey-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=20101006190343.GI2472@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=wey-yi.w.guy@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).