Linux wireless drivers development
 help / color / mirror / Atom feed
From: wwguy <wey-yi.w.guy@intel.com>
To: Lars Schotte <gusto@guttok.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn 3.0.9 aggreggation messages
Date: Mon, 14 Nov 2011 07:10:10 -0800	[thread overview]
Message-ID: <1321283410.13578.33.camel@wwguy-ubuntu> (raw)
In-Reply-To: <20111114131642.31e8ddbd@hana.gusto>

Hi Lars,

On Mon, 2011-11-14 at 04:16 -0800, Lars Schotte wrote:
> hi,
> 
> i get always such aggreggation messages every 35 seconds since the
> update from 3.0.8 to 3.0.9, so something is wrong there.
> 
> [  238.280312] iwlagn 0000:02:00.0: Aggregation not enabled for tid 0
> because load = 0 [  335.575672] iwlagn 0000:02:00.0:
> iwlagn_tx_agg_start on ra = 20:4e:7f:5b:2d:f5 tid = 0 [  400.605027]
> iwlagn 0000:02:00.0: iwlagn_tx_agg_start on ra = 20:4e:7f:5b:2d:f5 tid
> = 0 [  532.418136] iwlagn 0000:02:00.0: iwlagn_tx_agg_start on ra =
> 20:4e:7f:5b:2d:f5 tid = 0 [  590.173035] iwlagn 0000:02:00.0:
> iwlagn_tx_agg_start on ra = 20:4e:7f:5b:2d:f5 tid = 0 [  616.193084]
> iwlagn 0000:02:00.0: iwlagn_tx_agg_start on ra = 20:4e:7f:5b:2d:f5 tid
> = 0 [  934.882300] iwlagn 0000:02:00.0: iwlagn_tx_agg_start on ra =
> 20:4e:7f:5b:2d:f5 tid = 0 [  983.877888] iwlagn 0000:02:00.0:
> iwlagn_tx_agg_start on ra = 20:4e:7f:5b:2d:f5 tid = 0 [ 1048.354089]
> iwlagn 0000:02:00.0: iwlagn_tx_agg_start on ra = 20:4e:7f:5b:2d:f5 tid
> = 0 [ 1137.254697] iwlagn 0000:02:00.0: iwlagn_tx_agg_start on ra =
> 20:4e:7f:5b:2d:f5 tid = 0 [ 1173.956035] iwlagn 0000:02:00.0:
> iwlagn_tx_agg_start on ra = 20:4e:7f:5b:2d:f5 tid = 0

hmm, it should not happen, are you still seeing this in the latest
driver? if does, could you load the driver with debug flag = 0x43fff to
help us understand what is happening?

> 
> then there are no iwlagn drivers in 3.2 any more, but iwlwifi, what's
> the difference between these two drivers?
> 
We are in the process of re-architect and improve the flexible and
quality of our existing driver. As today, "iwlwifi" should the same as
"iwlagn" and you can use either one (iwlwifi or iwlagn), "iwlagn" just
an alias of "iwlwifi". Moving forward, we will deprecate the "iwlagn"
name after we complete the implementation of next generation of Intel
WiFi driver.

Thanks
Wey
 



  reply	other threads:[~2011-11-14 15:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 12:16 iwlagn 3.0.9 aggreggation messages Lars Schotte
2011-11-14 15:10 ` wwguy [this message]
2011-11-14 19:19   ` Lars Schotte
2011-11-14 20:38     ` wwguy
2011-11-14 21:13       ` Lars Schotte
2011-11-14 21:18       ` Lars Schotte
2011-11-14 21:22         ` wwguy
2011-11-14 21:47           ` Lars Schotte
2011-11-14 21:44             ` wwguy
2011-11-14 22:05               ` Lars Schotte
2011-11-14 22:28               ` Lars Schotte
2011-11-14 22:41                 ` wwguy
2011-11-14 22:56                   ` Lars Schotte
2011-11-14 22:59                     ` wwguy
2011-11-14 23:16                       ` Lars Schotte
2011-11-14 23:17                         ` wwguy
2011-11-14 23:30                           ` Lars Schotte
2011-11-14 23:31                             ` wwguy
2011-11-14 23:58                               ` Lars Schotte
2011-11-14 22:29               ` Lars Schotte
2011-11-14 21:27         ` wwguy
2011-11-14 21:50           ` Lars Schotte

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=1321283410.13578.33.camel@wwguy-ubuntu \
    --to=wey-yi.w.guy@intel.com \
    --cc=gusto@guttok.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