linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Reinette Chatre <reinette.chatre@intel.com>,
	linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3/5] iwlwifi: cleanup namespace
Date: Fri, 09 Nov 2007 09:53:41 +0800	[thread overview]
Message-ID: <1194573222.31257.366.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20071108182254.GA32063@lst.de>


On Thu, 2007-11-08 at 19:22 +0100, Christoph Hellwig wrote:
> Any chance we can get this whole patch series into 2.6.24?  It's just
> a blind cleanup of the symbols and having two new drivers that can't
> be built into the kernel or loaded into the kernel is rather
> embarassing.

No. It's not a that "simple" cleanup. We actually found a endless
recursive bug in your previous patch (already fixed in this one). There
is a static iwl_init_hw_rates() in iwl4965-base.c and there is also a
public iwl4965_init_hw_rates() in iwl-4965.c. When you do the string
replacement, it became a endless recursive for iwl4965_init_hw_rates().

Furthermore, although both of the drivers can be built into kernel at
the same time, it is useless if you do so now. Because if you make a
network driver build in the kernel, it is initialized in a very early
stage (before hd, sata). Currently the iwlwifi drivers (I think also
other wireless drivers) load the firmware in pci_probe(), we have to
move it to interface open() time to resolve this problem. But this is
not so easy as it looks like: iwlwifi drivers cannot get MAC address
before firmware is loaded and running, but mac80211 requires MAC address
from the driver when ieee80211_register_hw() is called.
ieee80211_register_hw() creates the wlan0 interface. You have no
interface if you don't call ieee80211_register_hw() at pci_probe()...

I'll come up a patch to delay the device MAC address get until
wlan0->start() is called for mac80211. So that I can delay the firmware
loading from pci probe to interface open time for iwlwifi drivers. In
conclusion, the patch only makes iwlwifi drivers compile but not work
for the kernel build in case. More patches will come. And we have to
target it for 2.6.25.

Thanks,
-yi

      reply	other threads:[~2007-11-09  2:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11944155883607-git-send-email-reinette.chatre@intel.com>
2007-11-07  6:06 ` [PATCH 1/5] iwlwifi: replace 0x8086 with PCI_VENDOR_ID_INTEL Reinette Chatre
2007-11-07  6:06   ` [PATCH 2/5] iwl4965: fix cannot find a suitable rate issue Reinette Chatre
     [not found]     ` <11944155923015-git-send-email-reinette.chatre@intel.com>
2007-11-07  6:06       ` [PATCH 4/5] remove unused iwl4965_init_hw_rates function Reinette Chatre
2007-11-07  6:06         ` [PATCH 5/5] MAINTAINERS: Add Reinette Chatre to iwlwifi & ipw2100/ipw2200 Reinette Chatre
2007-11-08 18:22       ` [PATCH 3/5] iwlwifi: cleanup namespace Christoph Hellwig
2007-11-09  1:53         ` Zhu Yi [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=1194573222.31257.366.camel@debian.sh.intel.com \
    --to=yi.zhu@intel.com \
    --cc=hch@lst.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=reinette.chatre@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).