linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Ketrenos <jketreno@linux.intel.com>
To: Michael Wu <flamingice@sourmilk.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH]  Add iwlwifi wireless drivers
Date: Tue, 22 May 2007 12:16:02 -0700	[thread overview]
Message-ID: <46534172.5040106@linux.intel.com> (raw)
In-Reply-To: <200705162151.32910.flamingice@sourmilk.net>

Michael Wu wrote:
> On Wednesday 16 May 2007 17:45, James Ketrenos wrote:
>> This patch adds the iwlwifi project directory and sources needed to
>> build the mac80211 based wireless drivers for the Intel PRO/Wireless
>> 3945ABG/BG Network Connection and Intel Wireless WiFi Link AGN adapters.
>>
> Looks much better than when I last checked. A few comments:

I've attempted to address everything not discussed below in the updated code.  That said --

> - Read and set the MAC address before calling ieee80211_register_hw.

We're calling SET_IEEE80211_PERM_ADDR before we call ieee80211_register_hw.  Is there something else we should be doing?

> - mac80211 (very recently) sets up a workqueue for the driver to use so you 
> don't need to create your own anymore.

In addition to the workqueue created when you call ieee80211_register_hw?  We need to have a workqueue for initializing the adapter and uCode before we call ieee80211_register_hw.  If ieee80211_alloc_hw created the workqueue, that would work for us (assuming there aren't going to be any side effects from us flushing the workqueue before we call ieee80211_free_hw/ieee80211_unregister_hw)

That said -- if the driver can execute in parallel to the stack for some operations, shouldn't they remain on their own workqueues so the work can be divided up vs. having *everything* routed through one singlethread workqueue?

> - Why are probe requests being dropped in adhoc mode? (assuming hardware 
> handles it.. but the message output for that doesn't sound like it)

It only drops them if the adapter is not in the associated state (the card is configured with the RXON_FLAG_ASSOC_MSK bit clear)

> - If you don't want to add a radiotap header all the time, you should check 
> the IEEE80211_CONF_RADIOTAP flag to see if a radiotap header is desired by 
> the stack. (not whether or not we're configured as IEEE80211_IF_TYPE_MNTR)

I have this on the todo list.  

Thanks for the time you spent looking over the code.

James


  parent reply	other threads:[~2007-05-22 20:39 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 21:45 [PATCH] Add iwlwifi wireless drivers James Ketrenos
2007-05-17  1:27 ` Randy Dunlap
2007-05-17  4:28   ` James Ketrenos
2007-05-17  5:57     ` Jeff Garzik
2007-05-22 21:38       ` James Ketrenos
2007-05-18 19:01   ` James Ketrenos
2007-05-18 20:57     ` Jeff Garzik
2007-05-18 20:54       ` James Ketrenos
2007-05-18 21:06     ` Randy Dunlap
2007-05-22 18:39       ` John W. Linville
2007-05-22 18:29         ` James Ketrenos
2007-05-17  1:51 ` Michael Wu
2007-05-17  2:56   ` Jeff Garzik
2007-05-17  3:55     ` Michael Wu
2007-05-17  8:52   ` Christoph Hellwig
2007-05-22 19:16   ` James Ketrenos [this message]
2007-05-22 23:00     ` Jeff Garzik
2007-05-22 21:49       ` James Ketrenos
2007-05-22 23:41         ` Jeff Garzik
2007-05-22 22:56           ` James Ketrenos
2007-05-23  0:58             ` Jeff Garzik
2007-05-23 18:17               ` James Ketrenos
2007-05-23 19:59                 ` Jeff Garzik
2007-05-23 19:30                   ` James Ketrenos
2007-05-23  1:06     ` Michael Wu
2007-05-23  1:46       ` Jeff Garzik
2007-05-17  3:35 ` [PATCH] Add iwlwifi wireless drivers [part 2/2] Randy Dunlap
2007-05-17 15:03   ` Stephen Hemminger
2007-05-17 15:05   ` Stephen Hemminger
2007-05-18  7:04     ` Johannes Berg
2007-05-18 20:33   ` James Ketrenos
2007-05-18 22:05     ` Jeff Garzik
2007-05-18 21:31       ` James Ketrenos
2007-05-18 22:50         ` Jeff Garzik
2007-05-18 23:04         ` Christoph Hellwig
2007-05-21 14:56           ` James Ketrenos
2007-05-21 16:26             ` Christoph Hellwig
2007-05-21 16:48               ` James Ketrenos
2007-05-21 18:15                 ` Christoph Hellwig
2007-05-21 20:12                   ` Cohen, Guy
2007-05-21 21:02                     ` Jeff Garzik
2007-05-21 21:10                       ` Randy Dunlap
2007-05-21 21:43                         ` Cohen, Guy
2007-05-21 22:15                           ` Jeff Garzik
2007-05-21 21:22                     ` Joerg Mayer
2007-05-21 21:46                       ` Cohen, Guy
2007-05-18 22:13     ` Randy Dunlap
2007-05-18 23:05 ` [PATCH] Add iwlwifi wireless drivers Christoph Hellwig
2007-05-18 23:22   ` Michael Wu
2007-05-22 21:50 ` [PATCH v3] " James Ketrenos
2007-05-23  1:06   ` Jeff Garzik
2007-05-23 15:16     ` James Ketrenos

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=46534172.5040106@linux.intel.com \
    --to=jketreno@linux.intel.com \
    --cc=flamingice@sourmilk.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).